# Is i18next ESM-only? Can you require() it?

> i18next@26.4.2 ships CommonJS and ESM builds. Dual package — require() works on every Node.js version we test; import works too.

i18next internationalization framework

Last verified Sep 9, 2026 against i18next@26.4.2.

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

1. 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.
2. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 26.4.2 (Sep 3, 2026)
- Module format: Dual (CommonJS + ESM)
- Last CommonJS version: 26.4.2
- Native ESM since: 21.5.0
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 19.7M
- License: MIT

## Runtime test results for i18next@26.4.2

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:

```js
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:

```js
const i18next = require("i18next");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (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

- [i18next on npm](https://www.npmjs.com/package/i18next)
- [Source repository](https://github.com/i18next/i18next)
- [HTML version](https://canirequire.com/package/i18next/)
- [JSON version](https://canirequire.com/package/i18next.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.