Book Image

Next.js Quick Start Guide

By : Kirill Konshin
Book Image

Next.js Quick Start Guide

By: Kirill Konshin

Overview of this book

Next.js is a powerful addition to the ever-growing and dynamic JavaScript world. Built on top of React, Webpack, and Babel, it is a minimalistic framework for server-rendered universal JavaScript applications. This book will show you the best practices for building sites using Next. js, enabling you to build SEO-friendly and superfast websites. This book will guide you from building a simple single page app to a scalable and reliable client-server infrastructure. You will explore code sharing between client and server, universal modules, and server-side rendering. The book will take you through the core Next.js concepts that everyone is talking about – hot reloading, code splitting, routing, server rendering, transpilation, CSS isolation, and more. You will learn ways of implementing them in order to create your own universal JavaScript application. You will walk through the building and deployment stages of your applications with the JSON API,customizing the confguration, error handling,data fetching, deploying to production, and authentication.
Table of Contents (9 chapters)

Internationalization and Localization

Any big app inevitably will have to be localized in order to widen the audience that can use the app. Besides using localized strings in the app, we also need to present dates and time in local format, and also might want to use pluralization for more human-readable messages. For date and time, the champion is MomentJS, and for pluralization, the ICU format is the most advanced one, so we picked Format Message as the library for that.

Here, we will show only one of the potential ways to localize the application. Next.js again brings some nuances because of its universal nature, so the way we have chosen fits perfectly for both client and server counterparts; for this example, we will use the I18Next library.

Let's install a few packages as usual; isomorphic-unfetch is needed since we will make fetch requests from the server too:

$ npm...