This is Wanderlog's fork of i18next. We publish it to npm as
@wanderlogapp/i18next.
The itineraries repo installs it with
"i18next": "npm:@wanderlogapp/i18next@…".
First, commit and push your change to the wanderlog branch. Check
https://github.com/wanderlog/i18next/tags for the latest version, and add 1 to
the last number. Make sure npm whoami prints wanderlogapp (if not, run
npm login). Then run:
VERSION='<substitute version here>' # e.g., VERSION='v23.8.1-wanderlog.4'
# Start wanderlog-built from the latest commit on the wanderlog branch
git fetch
git checkout wanderlog-built
git reset --hard origin/wanderlog
# Build, and commit the build output (it's gitignored on the
# wanderlog branch)
npm install
npm run build
git add -f dist index.v4.d.ts
# Rename the package for npm, and set its version (without the leading v)
npm pkg set name='@wanderlogapp/i18next' version="${VERSION#v}"
# Remove the prepare script: it runs husky, which isn't installed
npm pkg delete scripts.prepare
# Commit, tag, and push the release
git commit -am "[$VERSION] Release built version"
git tag "$VERSION"
git push -f origin wanderlog-built "$VERSION"
# Publish to npm. --ignore-scripts skips the package's build and install
# scripts, since the built files are already committed
npm publish --access public --ignore-scriptsThen, in itineraries, bump the version in the npm:@wanderlogapp/i18next@…
alias and run yarn install. New @wanderlogapp/* versions skip the
one-week age gate because of npmPreapprovedPackages in .yarnrc.yml.
i18next is a very popular internationalization framework for browser or any other javascript environment (eg. Node.js, Deno).
i18next provides:
- Flexible connection to backend (loading translations via xhr, ...)
- Optional caching, user language detection, ...
- Proper pluralizations
- Translation context
- Nesting, Variable replacement
- Flexibility: Use it everywhere
- Extensibility: eg. sprintf
- ...
For more information visit the website:
Our focus is providing the core to building a booming ecosystem. Independent of the building blocks you choose, be it react, angular or even good old jquery proper translation capabilities are just one step away.
The general i18next documentation is published on www.i18next.com and PR changes can be supplied here.
The react specific documentation is published on react.i18next.com and PR changes can be supplied here.
From the creators of i18next: localization as a service - locize.com
A translation management system built around the i18next ecosystem - locize.com.
With using locize you directly support the future of i18next.

