canirequire › CommonJS › anakjalanan
Is anakjalanan ESM-only? Can you require() it?
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
Last verified Sep 9, 2026 against anakjalanan@1.1.4. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
anakjalanan ships CommonJS only. require("anakjalanan") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "anakjalanan" 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("anakjalanan") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
- From ES modules use the default import: import anakjalanan from "anakjalanan"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for anakjalanan; declare the module yourself if you need them.
Does anakjalanan@1.1.4 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("anakjalanan") from a CommonJS file and import "anakjalanan" from an ES module.
| Runtime | require("anakjalanan") | import "anakjalanan" |
|---|---|---|
| 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 anakjalanan
ES modules (import)
import anakjalanan from "anakjalanan";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 anakjalanan = require("anakjalanan");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 (1 versions; the newest 1 shown).
| Versions | Format | First published |
|---|---|---|
| 1.1.4 | CommonJS | Mar 9, 2024 |
Frequently asked
Is anakjalanan ESM-only?
anakjalanan@1.1.4 is a CommonJS package. anakjalanan ships CommonJS only. require("anakjalanan") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "anakjalanan" 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 anakjalanan with ES module syntax?
Yes. import anakjalanan from "anakjalanan" 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 anakjalanan work in Bun?
Yes. import "anakjalanan" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does anakjalanan ship TypeScript types?
No. anakjalanan 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
- @alifd/babel-preset-next 2.0.0-betaCommonJS
- less-plugin-sass2less 1.2.0CommonJS
- acertea 1.1.6CommonJS
- aid-guard1 2.7.35Dual