locize documentation
Help Center
Blog
Sign in
locize.com
Search…
Introduction
Using locize
What's inside?
The different views
Checks/Issues
Using locize as a translator
Integration
Getting started
Instrumenting your code
API
Webhook
CLI
I18n Formats
File Formats
Guides / Tips & Tricks
Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators
Migrating an i18next project
Migrating from ...
More
InContext Editor
Figma Plugin
Versioning
Namespaces
Caching
Backend Fallback
Latency Optimization – Tips for Optimal Performance
Notifications
2-factor authentication
Convince Your Boss Letter
General questions
Powered By
GitBook
Migrating an i18next project
Migrating an existing backend from i18next is just changing a few lines of code.
Browser & node.js
Just use the
i18next-locize-backend
1
import
i18next
from
'i18next'
;
2
import
Backend
from
'i18next-locize-backend'
;
3
4
i18next
5
.
use
(
Backend
)
6
.
init
({
7
// ...other options
8
9
backend
:
{
10
projectId
:
'[PROJECT_ID]'
,
11
apiKey
:
'[API_KEY]'
,
12
referenceLng
:
'[LNG]'
13
}
14
});
Copied!
(You can find your projectId and API Key in your projects settings under the API Tab.)
Find more details and configuration options on the
github page
.
Here you will find an example on how you could migrate to locize when already using i18next.
And here a complete tutorial on how to best internationalize with i18next and locize.
Migrating your data
You can use our
command line tool
to copy your existing translations over to your locize project.
Previous
localistars
Next - Guides / Tips & Tricks
Migrating from ...
Last modified
11mo ago
Copy link
Contents
Browser & node.js
Migrating your data