canirequire › CommonJS › json-parse-even-better-errors
Is json-parse-even-better-errors ESM-only? Can you require() it?
JSON.parse with context information on error
Last verified Sep 9, 2026 against json-parse-even-better-errors@6.0.0. JSON
CommonJS CommonJS — require() works on every Node.js version
json-parse-even-better-errors ships CommonJS only. require("json-parse-even-better-errors") works everywhere. import "json-parse-even-better-errors" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Does json-parse-even-better-errors@6.0.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("json-parse-even-better-errors") from a CommonJS file and import "json-parse-even-better-errors" from an ES module.
| Runtime | require("json-parse-even-better-errors") | import "json-parse-even-better-errors" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4 | ✓ works | ✓ works |
How to import json-parse-even-better-errors
ES modules (import)
import jsonParseEvenBetterErrors from "json-parse-even-better-errors";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const jsonParseEvenBetterErrors = require("json-parse-even-better-errors");Module format by version
Derived from the type, main and exports fields of every stable release on npm (12 versions; the newest 12 shown).
| Versions | Format | First published |
|---|---|---|
| 2.0.0 – 6.0.0 | CommonJS | Sep 27, 2019 |
Frequently asked
Is json-parse-even-better-errors ESM-only?
json-parse-even-better-errors@6.0.0 is a CommonJS package. json-parse-even-better-errors ships CommonJS only. require("json-parse-even-better-errors") works everywhere. import "json-parse-even-better-errors" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import json-parse-even-better-errors with ES module syntax?
Yes. import jsonParseEvenBetterErrors from "json-parse-even-better-errors" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does json-parse-even-better-errors work in Bun?
Yes. import "json-parse-even-better-errors" loaded successfully in Bun 1.4 on Sep 9, 2026.
Does json-parse-even-better-errors ship TypeScript types?
No. json-parse-even-better-errors ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- globalthis 1.0.4CommonJS
- media-typer 2.0.0ESM-only
- env-paths 4.0.0ESM-only
- esprima 4.0.1CommonJS
- protobufjs 8.8.0CommonJS
- @aws-sdk/credential-provider-node 3.972.82CommonJS
- function.prototype.name 1.2.0CommonJS
- split2 4.2.0CommonJS