Pages in Next.js - Navigate Between Pages | Learn Next.js

!tags:: #lit✍/📰️article/highlights
!links::
!ref:: Pages in Next.js - Navigate Between Pages | Learn Next.js
!author:: nextjs.org

=this.file.name

Book cover of "Pages in Next.js - Navigate Between Pages | Learn Next.js"

Reference

Notes

Quote

Client-side navigation means that the page transition happens using JavaScript, which is faster than the default navigation done by the browser.
- No location available
-

Quote

Next.js does code splitting automatically, so each page only loads what’s necessary for that page. That means when the homepage is rendered, the code for other pages is not served initially.
- No location available
-

Quote

Furthermore, in a production build of Next.js, whenever Link components appear in the browser’s viewport, Next.js automatically prefetches the code for the linked page in the background.
- No location available
-


dg-publish: true
created: 2024-07-01
modified: 2024-07-01
title: Pages in Next.js - Navigate Between Pages | Learn Next.js
source: hypothesis

!tags:: #lit✍/📰️article/highlights
!links::
!ref:: Pages in Next.js - Navigate Between Pages | Learn Next.js
!author:: nextjs.org

=this.file.name

Book cover of "Pages in Next.js - Navigate Between Pages | Learn Next.js"

Reference

Notes

Quote

Client-side navigation means that the page transition happens using JavaScript, which is faster than the default navigation done by the browser.
- No location available
-

Quote

Next.js does code splitting automatically, so each page only loads what’s necessary for that page. That means when the homepage is rendered, the code for other pages is not served initially.
- No location available
-

Quote

Furthermore, in a production build of Next.js, whenever Link components appear in the browser’s viewport, Next.js automatically prefetches the code for the linked page in the background.
- No location available
-