Next.js: Difference between revisions

Revision as of 23:52, 21 January 2024

Revision as of 22:13, 12 February 2024

Line 61:

The main feature of Next.js is its use of server-side rendering to reduce the burden on web browsers and provide enhanced security{{Citation needed|date=August 2021}}. This can be done for any part of the application or the entire system, allowing for content-rich pages to be singled out for server-side rendering.<ref name=thakkar1 /> It can also be done only for first-time visitors, to reduce the burden on web browsers that have yet to download any of the site's assets.<ref name=thakkar2 /> The "hot reloading" feature detects changes as they are made and re-renders the appropriate pages so the server avoids the need to be restarted. This allows changes made to the application code to be immediately reflected in the web browser, though some browsers will require the page to be refreshed.<ref name=thakkar1 /> The software uses page-based routing for developer convenience and includes support for dynamic routing. Other features include hot-module replacement so that modules can be replaced live, automatic code splitting, which only includes code necessary to load the page, and page prefetching to reduce load time.<ref name=thakkar1 />

Next.js also supports Incremental Static Regeneration<ref>{{Cite web |title=Incremental Static Regeneration with Next.js |url=https://vercel.com/docs/concepts/next.js/incremental-static-regeneration |access-date=2022-03-06 |website=Vercel |language=en-US}}</ref> and static site generation - a compiled version of the website is usually built during build time and saved as a .next folder. When a user makes a request, the pre-built version which are static HTML pages are cached and sent to them. This makes the load time very fast, but it's not suitable for every website, becauseparticularly for interactive sites that change often and utilize a lot of user input will not be suitable.

== See also ==