Installation
Minimal setup
npm install next-intl
- Add the provider in
_app.js
.
import {NextIntlProvider} from 'next-intl';
export default function App({Component, pageProps}) { return ( <NextIntlProvider messages={pageProps.messages}> <Component {...pageProps} /> </NextIntlProvider> );}
- Provide messages on a page-level.
// pages/index.jsexport async function getStaticProps({locale}: GetStaticPropsContext) { return { props: { // You can get the messages from anywhere you like, but the recommended // pattern is to put them in JSON files separated by language and read // the desired one based on the `locale` received from Next.js. messages: await import(`../../messages/index/${locale}.json`) } };}
- Make sure you have internationalized routing set up or alternatively provide an explicit
locale
toNextIntlProvider
. - Use translations in your components!
Have a look at the example to explore a minimal working setup.
Further setup (recommended)
While the above mentioned setup is typically sufficient to use next-intl
in your Next.js app, there are a few additional steps that are recommended:
- Based on the features you need and the browsers you support, you might have to provide polyfills.
- If you're formatting dates and times, a time zone should be configured. By default, dates are formatted according to the time zone of the environment, which can lead to markup mismatches if the server and the user are located in different time zones. By supplying the
timeZone
explicitly, you can ensure that dates and times are rendered the same way on the server as well as the client. - If you're formatting relative dates and times, a global value for
now
can be useful. This ensures that the server and client will render the same markup. Especially if you use caching for the responses of the server, the likelyhood of mismatches increases. - To achieve consistent date, time and number formatting, it might be useful to set up global formats which ensure consistent formatting across the app.