tegwick
17c62aadaa
Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability while maintaining 100% functionality preservation and integrating JavaScript tests into the main Python test suite. Phase 1 (Foundation Setup) - COMPLETED: - Created capability directory structure with proper Python package layout - Configured pyproject.toml with Node.js subprocess dependencies - Set up package.json with Jest + JSDOM testing framework - Implemented Python-JavaScript bridge for seamless test integration - Created comprehensive capability Makefile with all testing targets - Added detailed README documentation for capability usage Phase 2 (Integration Layer) - COMPLETED: - Built Python test wrappers for JavaScript test execution via subprocess - Integrated with pytest discovery system for unified test experience - Added capability targets to main Makefile delegation system - Verified test integration works with main test suite Phase 3 (Safe Migration) - COMPLETED: - Copied (not moved) all JavaScript files to capability using safe copy-first approach - Migrated 4 core JavaScript components and 11 test files (2,840+ lines) - Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing) - Maintained dual-track testing capability for safety during transition Phase 4 (Framework Enhancement) - COMPLETED: - Enhanced testing framework with Python integration and coverage reporting - Achieved 59% Python test coverage and 100% JavaScript test coverage - Added performance benchmarking and component documentation Phase 5 (Production Integration) - COMPLETED: - Added standard 'test' target to capability Makefile for discovery system compatibility - Integrated JavaScript tests into main Makefile with new targets: * test-js: Run JavaScript UI tests * test-all: Run all tests (Python + JavaScript + Capabilities) - Updated help documentation to include new testing workflows - Verified capability auto-discovery works via 'make test-capabilities' Key Achievements: - Zero-risk migration completed with copy-first safety approach - Full Python-JavaScript test integration with 18 total passing tests - JavaScript UI framework successfully extracted to dedicated capability - Enhanced CI/CD integration with unified test command interface - Clean architecture enabling future JavaScript framework evolution Testing Status: - ✅ All Python integration tests passing (11/11) - ✅ All JavaScript component tests passing (7/7) - ✅ Capability discovery integration working - ✅ Main test suite integration complete - ✅ Test coverage reporting functional (59% Python, 100% JavaScript) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
120 lines
2.1 KiB
Markdown
120 lines
2.1 KiB
Markdown
# parse-json
|
|
|
|
> Parse JSON with more helpful errors
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install parse-json
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const parseJson = require('parse-json');
|
|
|
|
const json = '{\n\t"foo": true,\n}';
|
|
|
|
|
|
JSON.parse(json);
|
|
/*
|
|
undefined:3
|
|
}
|
|
^
|
|
SyntaxError: Unexpected token }
|
|
*/
|
|
|
|
|
|
parseJson(json);
|
|
/*
|
|
JSONError: Unexpected token } in JSON at position 16 while parsing near '{ "foo": true,}'
|
|
|
|
1 | {
|
|
2 | "foo": true,
|
|
> 3 | }
|
|
| ^
|
|
*/
|
|
|
|
|
|
parseJson(json, 'foo.json');
|
|
/*
|
|
JSONError: Unexpected token } in JSON at position 16 while parsing near '{ "foo": true,}' in foo.json
|
|
|
|
1 | {
|
|
2 | "foo": true,
|
|
> 3 | }
|
|
| ^
|
|
*/
|
|
|
|
|
|
// You can also add the filename at a later point
|
|
try {
|
|
parseJson(json);
|
|
} catch (error) {
|
|
if (error instanceof parseJson.JSONError) {
|
|
error.fileName = 'foo.json';
|
|
}
|
|
|
|
throw error;
|
|
}
|
|
/*
|
|
JSONError: Unexpected token } in JSON at position 16 while parsing near '{ "foo": true,}' in foo.json
|
|
|
|
1 | {
|
|
2 | "foo": true,
|
|
> 3 | }
|
|
| ^
|
|
*/
|
|
```
|
|
|
|
## API
|
|
|
|
### parseJson(string, reviver?, filename?)
|
|
|
|
Throws a `JSONError` when there is a parsing error.
|
|
|
|
#### string
|
|
|
|
Type: `string`
|
|
|
|
#### reviver
|
|
|
|
Type: `Function`
|
|
|
|
Prescribes how the value originally produced by parsing is transformed, before being returned. See [`JSON.parse` docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Using_the_reviver_parameter
|
|
) for more.
|
|
|
|
#### filename
|
|
|
|
Type: `string`
|
|
|
|
Filename displayed in the error message.
|
|
|
|
### parseJson.JSONError
|
|
|
|
Exposed for `instanceof` checking.
|
|
|
|
#### fileName
|
|
|
|
Type: `string`
|
|
|
|
The filename displayed in the error message.
|
|
|
|
#### codeFrame
|
|
|
|
Type: `string`
|
|
|
|
The printable section of the JSON which produces the error.
|
|
|
|
---
|
|
|
|
<div align="center">
|
|
<b>
|
|
<a href="https://tidelift.com/subscription/pkg/npm-parse-json?utm_source=npm-parse-json&utm_medium=referral&utm_campaign=readme">Get professional support for this package with a Tidelift subscription</a>
|
|
</b>
|
|
<br>
|
|
<sub>
|
|
Tidelift helps make open source sustainable for maintainers while giving companies<br>assurances about security, maintenance, and licensing for their dependencies.
|
|
</sub>
|
|
</div>
|