Updates the Next.js docs that describe `next-devtools-mcp` to match its 0.4.0 thin-connector shape (see vercel/next-devtools-mcp#145). The knowledge-base, migration/upgrade, and Cache Components tools are gone — docs now ship with Next.js in `node_modules/next/dist/docs/` and upgrades use the codemod — so the guides should no longer point agents at those tools. In the MCP guide (`mcp.mdx`), the Development Tools list drops "Knowledge Base", "Migration and Upgrade Tools", and "Caching Guide" in favor of a documentation gateway that points agents at the bundled docs, and the examples now describe reading bundled docs and running the codemod rather than querying a knowledge base. In the v16 upgrade guide, the "Using AI Agents with Next.js DevTools MCP" section no longer instructs users to run removed prompts (`Next Devtools, help me upgrade` / `migrate to cache components`); it points to the codemod plus runtime diagnostics. Should land with the next-devtools-mcp 0.4.0 release. <!-- NEXT_JS_LLM_PR -->
expire and revalidate values to handle Infinity and surface mistakes early (#95493)
expire and revalidate values to handle Infinity and surface mistakes early (#95493)
Getting Started
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 our Learn Next.js course to get started with Next.js.
- Visit the Next.js Showcase to see more sites built with Next.js.
Documentation
Visit https://nextjs.org/docs to view the full documentation.
Community
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.
Contributing
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.
Good First Issues:
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.
Security
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.