Wednesday, May 16th 2018
Next.js 6 and Nextjs.orgPosted by
This year, the ZEIT Day Keynote started by highlighting our Open Source projects including showing the metrics of Next.js. With over 25000 stars on GitHub and over 10000 websites are already powered by it, we're incredibly amazed at its growth and love seeing the increasing amount of projects depending on it.
We are proud today to introduce the production-ready Next.js 6, featuring:
- Zero-configuration static exports. No need for
_app.js, an extension point that enables page transitions, error boundaries and more
- Babel 7 and Fragment syntax
- Extended integration test suites with a strong focus on security
- Flow annotations in the core codebase
In addition to the 6.0 release, we're moving to feature Next.js on its very own homepage, nextjs.org, featuring:
- All the Next.js documentation in one place. No more lookups of the README file on GitHub
- Merging https://learnnextjs.com into https://nextjs.org/learn
- A showcase of the most impressive websites built with Next.js
Next.js focuses on the idea of pre-rendering as a means to achieve high performance. Pre-rendering comes in two forms:
- Server rendering: where each request triggers a render. As a result, the end-user doesn't have to wait for any JS to be downloaded to start consuming data
- Static rendering: where we output static files that can be served directly without any code execution on the server
Until now, static exporting in Next.js was very powerful but not sufficiently easy to use. It required setting up a manual route map even when no custom routes were in use.
With Next.js 6, we automatically generate the route map for you based on the content of your
pages/ directory. If you're not using advanced custom routing, you won't have to make any modifications to
next.config.js. Just run:
Next.js offers an extensibility point called
_document.js. If defined, it lets you override the very top-level document of your application, which renders the
_document.js allows for powerful extensibility, but it has some serious limitations. For example, React is not able to render
<body> directly on the client side, so
_document.js is mostly limited to the initial pre-rendering phase.
To enable some other powerful use cases, we're introducing
_app.js, which is the top-level component that wraps the outside of each page.
Some differences between
Let's look at some use cases that defining
In this example, each page can be independently accessed, pre-rendered and lazy-loaded. However, when we transition on the client side, smooth animations are possible.
We already had numerous examples of integrating data and state management frameworks like Apollo and Redux.
_app.js, however, it's now even simpler to include these. Here are a few examples:
React offers a component method called
componentDidCatch which enables you to capture and handle exceptions that bubble up from nested components on the client side.
In many cases, due to the unexpected nature of these exceptions, you might want to handle all of them equally at the top level.
We have upgraded Babel to its latest version: 7. With it comes some great new features and improvements.
React 16.2 introduced the
Fragment API, which allows you to express a list of elements without having to wrap them in an arbitrary HTML element like
Writing this can be tedious, with Next.js 6 you can use the new JSX fragment syntax to facilitate creating fragments:
If you have a directory nested in your Next.js applications that require a different Babel configuration, it's now possible to include a scoped
.babelrc file specifically in that directory
.babelrc # General .babelrc
.babelrc # This .babelrc only applies to this directory
Babel 7 features built-in support for TypeScript (previously only Flow was supported by Babel).
To start off, we highlight a sped-up video that shows you how to create a PWA with server-rendering from scratch in 5 minutes:
The opening video of
When you need to look up something quickly, just head to nextjs.org/docs:
The documentation will always reflect the latest stable version
Previously, we would recommend beginners to head to https://learnnextjs.com for a step-by-step guide (with quizzes!) on how to get started with Next.js
Now we've integrated it directly into nextjs.org/learn to make it even easier start learning:
The easiest way to start learning Next.js
Showcase of projects built with Next.js