canirequire › CommonJS › ast-types
Is ast-types ESM-only? Can you require() it?
Esprima-compatible implementation of the Mozilla JS Parser API
Last verified Sep 9, 2026 against ast-types@0.16.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
ast-types ships CommonJS only. require("ast-types") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=4. import "ast-types" 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("ast-types") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=4.
- From ES modules use the default import: import astTypes from "ast-types"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does ast-types@0.16.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("ast-types") from a CommonJS file and import "ast-types" from an ES module.
| Runtime | require("ast-types") | import "ast-types" |
|---|---|---|
| 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 ast-types
ES modules (import)
import astTypes from "ast-types";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 astTypes = require("ast-types");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 (174 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 0.8.5 – 0.16.3 | CommonJS | Jul 30, 2015 |
Frequently asked
Is ast-types ESM-only?
ast-types@0.16.3 is a CommonJS package. ast-types ships CommonJS only. require("ast-types") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=4. import "ast-types" 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 ast-types with ES module syntax?
Yes. import astTypes from "ast-types" 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 ast-types work in Bun?
Yes. import "ast-types" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does ast-types ship TypeScript types?
Yes. ast-types bundles its own type declarations; no @types package is needed.
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
- pkg-dir 9.0.0ESM-only
- regenerator-runtime 0.14.1CommonJS
- object-hash 3.0.0CommonJS
- @smithy/core 3.33.3Dual
- @radix-ui/react-popper 1.3.7Dual
- is-weakref 1.1.1CommonJS
- @radix-ui/react-roving-focus 1.1.19Dual
- @radix-ui/react-use-size 1.1.4Dual