# i18next-resources-to-backend
> This package helps to transform resources to an i18next backend
Latest version **1.2.3** (published 2026-07-31) · MIT license · 0 weekly downloads
## Install
```sh
npm install i18next-resources-to-backend
pnpm add i18next-resources-to-backend
yarn add i18next-resources-to-backend
bun add i18next-resources-to-backend
```
## Health
**Score 70/100 (B)** — status: active.
Positive: has types; esm support; no vulnerabilities; recently updated; high maintenance score; high quality score.
Warnings: low downloads.
## Facts
| | |
|---|---|
| Version | 1.2.3 |
| Published | 2026-07-31 |
| First published | 2021-05-24 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | bundled |
| Module format | ESM + CommonJS |
| Dependencies | 1 |
| Unpacked size | 26.5 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 66 |
| Maintainers | adrai |
| Keywords | i18next, i18next-backend, i18next-chained-backend |
## Links
- npm: https://www.npmjs.com/package/i18next-resources-to-backend
- Repository: https://github.com/i18next/i18next-resources-to-backend
- Issues: https://github.com/i18next/i18next-resources-to-backend/issues
- npm.io page: https://npm.io/package/i18next-resources-to-backend
## Dependencies (1)
- [@babel/runtime](https://npm.io/package/@babel/runtime.md) ^7.23.2
## Alternatives
- [messageformat](https://npm.io/package/messageformat.md) — 329.7K weekly downloads
- [@mintlify/scraping](https://npm.io/package/@mintlify/scraping.md) — 294.8K weekly downloads
- [@mintlify/previewing](https://npm.io/package/@mintlify/previewing.md) — 209.5K weekly downloads
- [@mintlify/prebuild](https://npm.io/package/@mintlify/prebuild.md) — 209.5K weekly downloads
- [@mintlify/link-rot](https://npm.io/package/@mintlify/link-rot.md) — 206.3K weekly downloads
## Recent versions
- 1.2.3 (latest) — 2026-07-31
- 1.2.2 — 2026-07-28
- 1.2.1 — 2024-04-10
- 1.2.0 — 2023-11-10
- 1.1.4 — 2023-05-19
- 1.1.3 — 2023-03-20
- 1.1.2 — 2023-02-24
- 1.1.1 — 2022-12-08
- 1.1.0 — 2022-12-07
- 1.0.0 — 2021-05-24
## README
# Introduction
[](https://github.com/i18next/i18next-resources-to-backend/actions?query=workflow%3Anode)
[](https://github.com/i18next/i18next-resources-to-backend/actions?query=workflow%3Adeno)
[](https://www.npmjs.com/package/i18next-resources-to-backend)
This package helps to transform resources to an i18next backend. To be used in Node.js, in the browser and for Deno.
## Advice:
If you don't like to manage your translation files manually or are simply looking for a [better management solution](https://www.locize.com?utm_source=i18next_resources_to_backend_readme&utm_medium=github&utm_campaign=readme), take a look at [i18next-locize-backend](https://github.com/locize/i18next-locize-backend) — translations served from a hosted CDN instead of bundled with your app. The i18next [backend plugin](https://www.i18next.com/overview/plugins-and-utils#backends) for 🌐 [Locize](https://www.locize.com?utm_source=i18next_resources_to_backend_readme&utm_medium=github&utm_campaign=readme) ☁️.
Starting from an app with hardcoded strings? Run `npx i18next-cli localize` — one command that wraps strings in `t()`, extracts keys, connects to [Locize](https://www.locize.com?from=i18next-resources-to-backend_readme__localize) and AI-translates your app. See the [launch post](https://www.locize.com/blog/i18next-cli-localize?from=i18next-resources-to-backend_readme__localize).
# Getting started
Source can be loaded via [npm](https://www.npmjs.com/package/i18next-resources-to-backend).
```bash
# npm package
$ npm install i18next-resources-to-backend
```
## simple example - dynamic imports (lazy load in memory translations)
i18next-resources-to-backend helps to transform resources to an i18next backend. This means you can lazy load translations.
The dynamic import must be passed a string. Webpack will fail to load the resource if you pass a variable to `import()`.
For example, when using webpack:
```js
import i18next from 'i18next';
import resourcesToBackend from 'i18next-resources-to-backend';
i18next
.use(resourcesToBackend((language, namespace) => import(`./locales/${language}/${namespace}.json`)))
.on('failedLoading', (lng, ns, msg) => console.error(msg);
.init({ /* other options */ })
```
## used as fallback in combination with another i18next backend
i.e. [Browser fallback with local / bundled translations](https://www.i18next.com/how-to/backend-fallback#browser-fallback-with-local-bundled-translations)
Wiring up:
```js
import i18next from 'i18next'
import ChainedBackend from 'i18next-chained-backend'
import resourcesToBackend from 'i18next-resources-to-backend'
import HttpBackend from 'i18next-http-backend'
i18next.use(ChainedBackend).init({
backend: {
backends: [
HttpBackend, // if a namespace can't be loaded via normal http-backend loadPath, then the inMemoryLocalBackend will try to return the correct resources
resourcesToBackend({
en: {
translations: {
sayHi: 'hello world'
}
}
})
],
backendOptions: [{
loadPath: 'http://localhost:8080/locales/{{lng}}/{{ns}}.json'
}]
}
})
```
for Deno:
```js
import i18next from 'https://deno.land/x/i18next/index.js'
import ChainedBackend from 'https://deno.land/x/i18next_chained_backend/index.js'
import resourcesToBackend from 'https://deno.land/x/i18next_resources_to_backend/index.js'
import HttpBackend from 'https://deno.land/x/i18next_http_backend/index.js'
i18next.use(ChainedBackend).init({
backend: {
backends: [
HttpBackend, // if a namespace can't be loaded via normal http-backend loadPath, then the inMemoryLocalBackend will try to return the correct resources
resourcesToBackend({
en: {
translations: {
sayHi: 'hello world'
}
}
})
],
backendOptions: [{
loadPath: 'http://localhost:8080/locales/{{lng}}/{{ns}}.json'
}]
}
})
```
## you can also lazy load the in memory translations, i.e. when using webpack:
```js
i18next.use(ChainedBackend).init({
backend: {
backends: [
HttpBackend, // if a namespace can't be loaded via normal http-backend loadPath, then the inMemoryLocalBackend will try to return the correct resources
// with dynamic import, you have to use the "default" key of the module ( https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#importing_defaults )
resourcesToBackend((language, namespace) => import(`./locales/${language}/${namespace}.json`))
// resourcesToBackend((language, namespace, callback) => {
// import(`./locales/${language}/${namespace}.json`)
// .then(({ default: resources }) => {
// callback(null, resources)
// })
// .catch((error) => {
// callback(error, null)
// })
// })
],
backendOptions: [{
loadPath: 'http://localhost:8080/locales/{{lng}}/{{ns}}.json'
}]
}
})
```
---
Gold Sponsors
---
**From the creators of i18next: localization as a service - locize.com**
A translation management system built around the i18next ecosystem - [locize.com](https://www.locize.com?utm_source=i18next_resources_to_backend_readme&utm_medium=github&utm_campaign=readme).
With using [Locize](https://www.locize.com/?utm_source=i18next_resources_to_backend_readme&utm_medium=github&utm_campaign=readme) you directly support the future of i18next.
---
---
_Source: https://npm.io/package/i18next-resources-to-backend · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._