React 16 introduced streaming server-side rendering, which allows you to send down HTML in chunks in parallel to rendering it. This enables a faster time to first byte and first meaningful paint for your users since the first markup arrives in the browser sooner.
Streams are also asynchronous, contrary to
renderToString, and handle backpressure well. This enables your Node.js server to render multiple requests at the same time and stay responsive in challenging conditions. It can pause React’s rendering if the network is saturated, and makes it so heavier requests doesn’t block lighter requests for a prolonged period of time.
Since we were having some performance issues in our server-side rendering worker for Spectrum we recently implemented streaming, which turned out to have an interesting downstream impact on our caching. Let's look at how we implemented it!
In certain situations, you might need immediate answers to your questions about our products and their features. Previously, we only offered help over email@example.com and the community chat (including our social network accounts).
As of today, we are also providing special support add-ons, which come with guaranteed response times: 24 hours, 12 hours and in real-time. This post describes each add-on's purpose and what you can expect from it.
We are very happy to introduce Next.js 5.0 to the world. It’s available on npm effective immediately. To upgrade, run:
In addition to bumping Next.js, we upgrade the peer dependencies
Next.js is a toolkit for universal, server-rendered (or statically pre-rendered) React.js applications. Getting started developing an application of any size is as easy as executing
next. (Read more.)
With every new release we are committed to retaining backwards compatibility, offering simple upgrade paths and only making API changes when absolutely necessary. Next.js 5.0 is no exception.
Under the hood, however, Next.js has undergone a radical transformation to enable powerful new use cases and extensibility. We started by making Next.js share a universal Webpack pipeline for both server and client code.
Today we are introducing the web counterpart to our command-line domain acquisition feature.
ZEIT Domains is powered by Now serverless deployments, automatically scaled to North America and Europe. It makes use of Next.js combined with React Fiber features to bring your results with as little latency as possible.
Read on to learn not just how this feature works, but also how it was built.
In order to assist the building of your own tools and the extension of our platform, we are introducing the second major iteration of our API with support for geographic distribution, simpler API calls, OAuth 2.0 and overhauled API docs.
With this release, we aimed for making the API much more accessible, consistent and fault-tolerant. Read on to understand how we accomplished this and what else is in store for your team.