Next.js has reached version 8. Next.js is a React framework for static and server applications. The latest version includes features such as Server.js without the server, massive reduction in memory usage at construction time, the configuration of the environment at construction time, previous search performance improvements and a smaller initial HTML size. Next.js 8 allows serverless deployment, in which applications are divided into smaller parts, or lambdas, which allow the code to run on demand and expand automatically. In Next.js Version 8, each page in the page directory becomes a lambda without a server. A low-level API is available for serverless deployment. The same has been shown below:
The Next.js team, together with the Webpack team, has worked to improve the compilation performance and resource utilization of Next.js and Webpack. This collaboration has resulted in up to 16 times better memory usage without degradation in performance. This improvement guarantees that the memory is released much more quickly and that the processes under stress are not blocked.
In Next.js 8, the “prefetch” attribute uses the rel = “preload” link instead of a “script” tag. Now, the previous search starts after loading to allow the browser to manage the resources. Next.js supports the previous search of pages for faster navigation. Previously, users had to inject a “script” tag into the “body” of the document, which caused an overload when opening pages. In addition to eliminating overload, this version also disables pre-fetching on slower network connections by detecting the 2G model of the internet and navigator.connection.aveData
For complete documentation of Next.js, you can click here
The serverless deployment comes with several benefits that include more reliability, scalability, and separation of concerns by splitting an application into smaller parts. These smaller parts are also called as lambdas. To provide these benefits of the serverless implementation to Next.js users, this version comes with a serverless mode in which each page in the “page” directory will be treated as a lambda. It will also come with a low-level API to implement the serverless implementation.
In which static rendering through the next export will be faster on multi-CPU machines. Static rendering is done to output files that can be served directly without code execution on the server. The number of CPU cores will be detected automatically and pages distributed accordingly.
You can find another latest updates introduced in Next.js 8 by clicking here.
We Brew Our Blogs Especially For Startups, Agencies & CTOs. Subscribe & Get Latest Updates Straight To Your Inbox
Save Upto 50% Of Development Cost and Get 2x Faster DeliveryCONTACT US
We all want websites to load faster. The users of every website are looking for a faster, easier experience. Overall, the size of the sites are getting bigger and need […] - Read More
Owners of WordPress-based websites should update the Jetpack plug-in as soon as possible because of a serious flaw that could expose their users to attacks. Jetpack […] - Read More
Here we will use API of Ig labs (www.labs.ig.com). Our first step here will first authenticate us to the server with our username+password+api keys. I will explain one […] - Read More
Google has launched Google Play Security Reward Program just a few days back in coordination with bug bounty platform HackerOne. However, Google itself runs its own bug […] - Read More
PHP or Hypertext Processor is a server-side scripting language, which is very popular among web developers, thanks to highly flexible syntax with flawlessly work in […] - Read More