canirequire › CommonJS › jsonwebtoken
Is jsonwebtoken ESM-only? Can you require() it?
JSON Web Token implementation (symmetric and asymmetric)
Last verified Sep 9, 2026 against jsonwebtoken@9.0.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
jsonwebtoken ships CommonJS only. require("jsonwebtoken") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=12. import "jsonwebtoken" 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.
What to do
- require("jsonwebtoken") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=12.
- From ES modules use the default import: import jsonwebtoken from "jsonwebtoken"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/jsonwebtoken
Does jsonwebtoken@9.0.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("jsonwebtoken") from a CommonJS file and import "jsonwebtoken" from an ES module.
| Runtime | require("jsonwebtoken") | import "jsonwebtoken" |
|---|---|---|
| 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.0 | ✓ works | ✓ works |
How to import jsonwebtoken
ES modules (import)
import jsonwebtoken from "jsonwebtoken";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 jsonwebtoken = require("jsonwebtoken");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (82 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 4.2.1 – 9.0.3 | CommonJS | Mar 17, 2015 |
Frequently asked
Is jsonwebtoken ESM-only?
jsonwebtoken@9.0.3 is a CommonJS package. jsonwebtoken ships CommonJS only. require("jsonwebtoken") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=12. import "jsonwebtoken" 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 jsonwebtoken with ES module syntax?
Yes. import jsonwebtoken from "jsonwebtoken" 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 jsonwebtoken work in Bun?
Yes. import "jsonwebtoken" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does jsonwebtoken ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/jsonwebtoken".
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
- pure-rand 8.4.2Dual
- array-includes 3.1.9CommonJS
- setimmediate 1.0.5CommonJS
- loader-utils 3.3.1CommonJS
- es-shim-unscopables 1.1.0CommonJS
- strnum 2.4.2ESM-only
- babel-plugin-istanbul 8.0.0CommonJS
- @radix-ui/react-tabs 1.1.21Dual