
The React Framework for full-stack web apps
Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful Rust-based JavaScript tooling for the fastest builds.
Visit https://nextjs.org/docs to view the full documentation.
The Next.js community can be found on GitHub Discussions where you can ask questions, voice ideas, and share your projects with other people.
To chat with other community members, you can join the Next.js Discord server.
Do note that our Code of Conduct applies to all Next.js community channels. Users are highly encouraged to read and adhere to it to avoid repercussions.
Contributions to Next.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our Contribution Guidelines to make sure you have a smooth experience contributing to Next.js.
We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process.
If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and NOT open a public issue.
To participate in our Open Source Software Bug Bounty program, please email [email protected]. We will add you to the program and provide further instructions for submitting your report.
[App Router] Critical layout CSS lacks preload link hints in document head
notFound() serves an empty `__next_error__` document instead of not-found.tsx
Mount-time setState in a layout-level client ancestor forces client render of a pending streamed Suspense boundary (no error; startTransition doesn't help)
Redirects from proxy drop the _rsc search param, while rewrites and next.config redirects keep it
Next.js >=16.0.0: Mismatch in RSC file paths causes 404 errors in static exports on Windows
`next/link` prefetches across routers in mixed App/Pages apps (`_next/data` 404 for App routes, HTML prefetch for Pages routes)
Route announcer crashes with `removeChild` after browser translation
cacheHandlers[*].updateTags only receives the first profile group when one request revalidates tags with different profiles
WASM: codeFrameColumns rejects `color: boolean` and `maxWidth: undefined`, which the napi binding and Next's own callers accept
Malformed percent-encoding in an App Router dynamic segment returns 500 instead of 400