8839075805
Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <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>
|