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-intl
Tim Neutkens 7f0591896a Use latest version of Next for all examples (#1597)
* Use latest for all examples

* Update yarn.lock
2017-04-03 09:46:35 +05:30
..
components Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
lang Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
pages Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
scripts Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
.babelrc Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
.gitignore Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
package.json Use latest version of Next for all examples (#1597) 2017-04-03 09:46:35 +05:30
README.md Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00
server.js Add example app with React Intl (#1055) 2017-02-24 22:45:18 +01:00

Example app with React Intl

How to use

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/with-react-intl
cd with-react-intl

Install it and run:

npm install
npm run dev

Deploy it to the cloud with now (download)

now

The idea behind the example

This example app shows how to integrate React Intl with Next.

Features of this example app

  • Server-side language negotiation
  • React Intl locale data loading via pages/_document.js customization
  • React Intl integration at Next page level via pageWithIntl() HOC
  • <IntlProvider> creation with locale, messages, and initialNow props
  • Default message extraction via babel-plugin-react-intl integration
  • Translation management via build script and customized Next server

Translation Management

This app stores translations and default strings in the lang/ dir. This dir has .messages/ subdir which is where React Intl's Babel plugin outputs the default messages it extracts from the source code. The default messages (en.json in this example app) is also generated by the build script. This file can then be sent to a translation service to perform localization for the other locales the app should support.

The translated messages files that exist at lang/*.json are only used during production, and are automatically provided to the <IntlProvider>. During development the defaultMessages defined in the source code are used. To prepare the example app for localization and production run the build script and start the server in production mode:

$ npm run build
$ npm start

You can then switch your browser's language preferences to French and refresh the page to see the UI update accordingly.