canirequire › Dual (CommonJS + ESM) › i18next
Is i18next ESM-only? Can you require() it?
i18next internationalization framework
Last verified Sep 9, 2026 against i18next@26.4.2. Markdown · JSON
Dual (CommonJS + ESM) Dual package — require() works on every Node.js version we test; import works too
i18next publishes both a CommonJS entry and a native ESM entry (ESM added in 21.5.0). require("i18next") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "i18next" works alongside it.
What to do
- Nothing to change. require("i18next") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import * as i18next from "i18next" works alongside it; use named imports for what the ESM entry exports.
- TypeScript: types are bundled; install nothing extra.
Does i18next@26.4.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("i18next") from a CommonJS file and import "i18next" from an ES module.
| Runtime | require("i18next") | import "i18next" |
|---|---|---|
| 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 i18next
ES modules (import)
import * as i18next from "i18next";Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.
CommonJS (require)
const i18next = require("i18next");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 (583 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 25.7.1 – 26.4.2 | Dual (CommonJS + ESM) | Dec 1, 2025 |
Frequently asked
Is i18next ESM-only?
i18next@26.4.2 ships CommonJS and ESM builds. i18next publishes both a CommonJS entry and a native ESM entry (ESM added in 21.5.0). require("i18next") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "i18next" works alongside it.
Can I require i18next?
Yes. i18next ships a CommonJS entry alongside the native ESM entry. require("i18next") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
Does i18next work in Bun?
Yes. import "i18next" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does i18next ship TypeScript types?
Yes. i18next bundles its own type declarations; no @types package is needed.
Links
Other dual (commonjs + esm) packages
- minimatch 10.2.6Dual
- brace-expansion 5.0.9Dual
- lru-cache 11.5.2Dual
- tslib 2.8.1Dual
- glob 13.0.6Dual
- eslint-visitor-keys 5.0.1Dual
- yallist 5.0.0Dual
- balanced-match 4.0.4Dual
Similar popularity
- @openai/codex 0.153.4No entry
- change-case 5.4.4ESM-only
- boxen 8.0.1ESM-only
- underscore 1.13.8Dual
- lodash.clonedeep 4.5.0CommonJS
- storybook 10.6.0ESM-only
- @rollup/plugin-commonjs 29.0.3Dual
- clean-css 5.3.3CommonJS