krakenjs / load-jsonic-sync

A simple synchronous JSON-with-comments loader that gives good explanations of where failures come from

load-jsonic-sync

A simple synchronous JSON-with-comments loader that gives good explanations of where failures come from.

It accepts a superset of JSON including Javscript style comments (/* */ and //).

Use

var loadJsonicSync = require('load-jsonic-sync');

var result = loadJsonicSync('file.json');

loadJsonicSync will throw an error if loading fails. The error will show the filename, for context, and error.cause() will show the original exception which includes the position for parse errors, and the underlying fs error if there is a problem reading the file.

load-jsonic-sync's Issues

load-jsonic-sync transitively depends on exploitable version of uglify-js

Copied from ExpediaGroup/determination#1 :

https://nodesecurity.io/advisories/39
https://nodesecurity.io/advisories/48

│ │ ├─┬ [email protected]
│ │ │ ├─┬ [email protected]
│ │ │ │ ├── [email protected]
│ │ │ │ └─┬ [email protected]
│ │ │ │   ├── [email protected]
│ │ │ │   ├── [email protected]
│ │ │ │   └── [email protected]

module misses parity with "shush"

This module was added as a replacement for shush. But it does not account for files specified without their .json extension. Recommend fixing that here so the confit implementation doesn't have to account for the same.

Compatibility with node 14

This is the problem:

(node:22719) Warning: Accessing non-existent property 'BSJSParser' of module exports inside circular dependency (node:22719) Warning: Accessing non-existent property 'BSJSIdentity' of module exports inside circular dependency (node:22719) Warning: Accessing non-existent property 'BSJSTranslator' of module exports inside circular dependency

I realized that Node 12 allow this circular dependencies, but Node 14 no, so that’s why those warnings, discover where this is happening and is in the node_modules on a ometajs dependencies, all the ometajs related, as this is.

Any suggestion to fix this?