Skip to content

beenotung/best-effort-json-parser

Repository files navigation

best-effort-json-parser

Parse incomplete JSON text in best-effort manner. Useful for partial JSON responses, broken network packages, LLM responses with markdown fences or exceeding token limits, and configuration files with comments.

npm Package Version Minified Package Size Minified and Gzipped Package Size npm Package Downloads

Features

  • Typescript support
  • Isomorphic package: works in Node.js and browsers
  • Comment support: // inline, /* multi-line */, and <!-- HTML-style --> comments
  • Markdown code block support: extracts JSON from ```json or ``` fences during parsing; remaining text is available via parse.lastParseReminding

Installation

npm install best-effort-json-parser

You can also install best-effort-json-parser with pnpm, yarn, or slnpm

Usage Example

Parsing incomplete JSON text

If the string, object, or array is not complete, the parser will return the partial data.

import { parse } from 'best-effort-json-parser'

let data = parse(`[1, 2, {"a": "apple`)
console.log(data) // [1, 2, { a: 'apple' }]

Parsing JSON with comments

Multiple types of comments are supported:

import { parse } from 'best-effort-json-parser'

let config = parse(`{
  "database": {
    "host": "localhost", // database server
    "port": 5432, /* default port */
    "ssl": true
  },
  "features": ["auth", "api"] <!-- injected by LLM -->
}`)

Comments inside strings are preserved and not treated as comments:

let data = parse(`{
  "inline_comment": "// this is not a comment",
  "block_comment": "/* neither is this */",
  "html_comment": \`<!-- \${variable} -->\`,
  "value": 42
}`)

Note: The parser also supports template literals with backticks (`) for strings, in addition to single and double quotes.

Parsing JSON in markdown code blocks

When LLMs return JSON inside markdown fences, parse() extracts the first block automatically:

import { parse } from 'best-effort-json-parser'

let llmResponse = `\`\`\`json
[
  {"id": 1, "username": "alice"},
  {"id": 2, "username": "bob"}
]
\`\`\``

let data = parse(llmResponse)
console.log(data) // [{ id: 1, username: 'alice' }, { id: 2, username: 'bob' }]

Both ```json and plain ``` fences are supported. If no fence is found, the input is parsed as-is.

When the response contains multiple fenced blocks, loop on parse.lastParseReminding to parse each block until it's empty.

Text after fences is also parsed. Most of them will be parsed as string, but substrings like true or 123 can become boolean or number, so filter by the JSON shape you expect from the markdown text (e.g. array or object):

Given markdown text with multiple fenced blocks:

Part 1:

```json
[
  { "id": 1, "username": "alice" },
  { "id": 2, "username": "bob" }
]
```

Part 2:

```
[
  { "id": 3, "username": "charlie" },
  { "id": 4, "username": "david" }
]
```

Ending text.
let parts: any[] = []
for (let acc = text; acc; acc = parse.lastParseReminding!) {
  parts.push(parse(acc))
}
// expect arrays from the LLM — skip prose parsed as string/number/boolean
parts = parts.filter(part => Array.isArray(part))

// if you expect objects instead:
// parts = parts.filter(part => typeof part === 'object' && part !== null && !Array.isArray(part))

// parts[0] => [{ id: 1, username: 'alice' }, { id: 2, username: 'bob' }]
// parts[1] => [{ id: 3, username: 'charlie' }, { id: 4, username: 'david' }]

Fences inside JSON string values are preserved and not treated as markdown:

let data = parse(`{
  "snippet": "\`\`\`json\\n[1,2,3]\\n\`\`\`"
}`)
// { snippet: '```json\n[1,2,3]\n```' }

Error Logging

By default, the parser logs errors to console.error. You can control error logging behavior:

import {
  disableErrorLogging,
  enableErrorLogging,
  setErrorLogger,
} from 'best-effort-json-parser'

// Disable error logging completely
disableErrorLogging()

// Re-enable error logging (default behavior)
enableErrorLogging()

// Set a custom error logger
setErrorLogger((message, data) => {
  // Your custom logging logic here
  console.log('Custom error:', message, data)

  // Common destinations for error data:
  // - Database storage for analysis
  // - File system logging
  // - Third-party services (Sentry, LogRocket, etc.)
  // - Monitoring and alerting systems
})

Typescript Signature

// Main parse function
function parse(s: string | undefined | null): any

// Parse namespace with additional properties
namespace parse {
  lastParseReminding: string | undefined // remaining text after the last parse (e.g. trailing markdown blocks)
  onExtraToken: (text: string, data: any, reminding: string) => void | undefined
}

// Error logging functions
function setErrorLogger(logger: (message: string, data?: any) => void): void
function disableErrorLogging(): void
function enableErrorLogging(): void

See more examples in parse.spec.ts

License

This is free and open-source software (FOSS) with BSD-2-Clause License

About

Parse incomplete JSON text in best-effort manner. Useful for partial JSON responses, broken network packages, LLM responses with markdown fences or exceeding token limits, and configuration files with comments.

Resources

License

Stars

278 stars

Watchers

2 watching

Forks

Packages

 
 
 

Contributors