1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
next.js/examples/with-react-i18next
2017-08-01 07:29:52 +05:30
..
components adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00
locales adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00
pages adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00
i18n.js Fix typo (#2692) 2017-08-01 07:29:52 +05:30
package.json adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00
README.md adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00
server.js adds with react-i18next example (#2558) 2017-07-16 22:19:45 +02:00

Getting started

Example with react-i18next.

# npm install
# npm run dev

open:

auto detecting user language: http://localhost:3000

german: http://localhost:3000/?lng=de

english: http://localhost:3000/?lng=en

The idea behind the example

This example app shows how to integrate react-i18next with Next.

Plus:

  • Routing and separating translations into multiple files (lazy load them on client routing)
  • Child components (pure or using translation hoc)

Features of this example app

  • Server-side language negotiation
  • Full control and usage of i18next on express server using i18next-express-middleware which asserts no async request collisions resulting in wrong language renderings
  • Support for save missing features to get untranslated keys automatically created locales/{lng}/{namespace}.missing.json -> never miss to translate a key
  • Proper pass down on translations via initialProps
  • Taking advantage of multiple translation files including lazy loading on client (no need to load all translations upfront)
  • Use express to also serve translations for clientside
  • In contrast to react-intl the translations are visible both during development and in production

learn more

Translation features:

Translation management: