0d5bf65feb
This pull request completely replaces our old page loader with a brand new route loader. Our existing comprehensive test suite means I did not need to add a bunch of tests. I did add them where behavior was added or fixed. Summary of the changes: - Eagerly evaluates prefetched pages in browser idle time (speeds up transitions) - Router is **no longer frozen** indefinitely if the Build Manifest never arrives - Router is **no longer frozen** indefinitely if a page fails to bootstrap - New `withFuture` utility instead of ad-hoc deduping per resource - Prefetching is now delayed until browser idle time to not impact TTI - Browsers without `prefetch` now fall back to eager evaluation instead of using `preload` - We're now ready to serve non-static assets **with `no-store` without breaking prefetching** - **Application can now hydrate without fetching CSS assets—this is a huge performance win that was previously blocking hydration** --- The minor size increase here is unfortunate, but we have to incur it for correctness. --- Fixes #18389 Fixes #18642 |
||
---|---|---|
.. | ||
bin | ||
build | ||
bundles/babel | ||
cli | ||
client | ||
compiled | ||
export | ||
lib | ||
next-server | ||
pages | ||
server | ||
telemetry | ||
types | ||
amp.d.ts | ||
amp.js | ||
app.d.ts | ||
app.js | ||
babel.d.ts | ||
babel.js | ||
client.d.ts | ||
client.js | ||
config.d.ts | ||
config.js | ||
constants.d.ts | ||
constants.js | ||
data.d.ts | ||
data.js | ||
document.d.ts | ||
document.js | ||
dynamic.d.ts | ||
dynamic.js | ||
error.d.ts | ||
error.js | ||
head.d.ts | ||
head.js | ||
image.d.ts | ||
image.js | ||
license.md | ||
link.d.ts | ||
link.js | ||
package.json | ||
README.md | ||
router.d.ts | ||
router.js | ||
taskfile-babel.js | ||
taskfile-ncc.js | ||
taskfile.js | ||
tsconfig.json |
Getting Started
Visit https://nextjs.org/learn to get started with Next.js.
Documentation
Visit https://nextjs.org/docs to view the full documentation.
Who is using Next.js?
Next.js is used by the world's leading companies. Check out the Next.js Showcase to learn more.
Community
The Next.js community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.
To chat with other community members you can join the Next.js Discord.
Our Code of Conduct applies to all Next.js community channels.
Contributing
Please see our contributing.md.
Authors
- Arunoda Susiripala (@arunoda) – Vercel
- Tim Neutkens (@timneutkens) – Vercel
- Naoyuki Kanezawa (@nkzawa) – Vercel
- Tony Kovanen (@tonykovanen) – Vercel
- Guillermo Rauch (@rauchg) – Vercel
- Dan Zajdband (@impronunciable) – Knight-Mozilla / Coral Project