Gathering detailed insights and metrics for json-parse-even-better-errors
Gathering detailed insights and metrics for json-parse-even-better-errors
Gathering detailed insights and metrics for json-parse-even-better-errors
Gathering detailed insights and metrics for json-parse-even-better-errors
npm install json-parse-even-better-errors
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
21 Stars
83 Commits
4 Forks
3 Watching
2 Branches
65 Contributors
Updated on 20 Nov 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-5.9%
8,219,818
Compared to previous day
Last week
2.1%
46,834,059
Compared to previous week
Last month
6.3%
197,186,911
Compared to previous month
Last year
33.1%
2,081,998,943
Compared to previous year
3
json-parse-even-better-errors
is a Node.js library for getting nicer errors out of JSON.parse()
,
including context and position of the parse errors.
It also preserves the newline and indentation styles of the JSON data, by
putting them in the object or array in the Symbol.for('indent')
and
Symbol.for('newline')
properties.
$ npm install --save json-parse-even-better-errors
1const parseJson = require('json-parse-even-better-errors') 2 3parseJson('"foo"') // returns the string 'foo' 4parseJson('garbage') // more useful error message 5parseJson.noExceptions('garbage') // returns undefined
noExceptions
method that returns undefined rather than throwing.Symbol.for('newline')
property on objects and arrays.Symbol.for('indent')
property on objects and arrays.To preserve indentation when the file is saved back to disk, use
data[Symbol.for('indent')]
as the third argument to JSON.stringify
, and
if you want to preserve windows \r\n
newlines, replace the \n
chars in
the string with data[Symbol.for('newline')]
.
For example:
1const txt = await readFile('./package.json', 'utf8') 2const data = parseJsonEvenBetterErrors(txt) 3const indent = Symbol.for('indent') 4const newline = Symbol.for('newline') 5// .. do some stuff to the data .. 6const string = JSON.stringify(data, null, data[indent]) + '\n' 7const eolFixed = data[newline] === '\n' ? string 8 : string.replace(/\n/g, data[newline]) 9await writeFile('./package.json', eolFixed)
Indentation is determined by looking at the whitespace between the initial
{
and [
and the character that follows it. If you have lots of weird
inconsistent indentation, then it won't track that or give you any way to
preserve it. Whether this is a bug or a feature is debatable ;)
parse(txt, reviver = null, context = 20)
Works just like JSON.parse
, but will include a bit more information when
an error happens, and attaches a Symbol.for('indent')
and
Symbol.for('newline')
on objects and arrays. This throws a
JSONParseError
.
parse.noExceptions(txt, reviver = null)
Works just like JSON.parse
, but will return undefined
rather than
throwing an error.
class JSONParseError(er, text, context = 20, caller = null)
Extends the JavaScript SyntaxError
class to parse the message and provide
better metadata.
Pass in the error thrown by the built-in JSON.parse
, and the text being
parsed, and it'll parse out the bits needed to be helpful.
context
defaults to 20.
Set a caller
function to trim internal implementation details out of the
stack trace. When calling parseJson
, this is set to the parseJson
function. If not set, then the constructor defaults to itself, so the
stack trace will point to the spot where you call new JSONParseError
.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More