Aurora ScharffandGitHub
d321ec8aa1
## What Updates the Next.js 16 upgrade guide's AI-agent section to present: - a recommended agent-assisted upgrade path - a dedicated docs setup section using `npx @next/codemod@canary agents-md` - a copy prompt that points to the guide's own docs setup and codemod sections, uses the Version 16 guide as the source of truth, asks the agent to communicate tradeoffs, verify with the AI-agent runtime flow such as `next-dev-loop` when available, and repeat the post-upgrade docs check - a non-agent path that keeps the existing upgrade codemod instructions It also removes the stale external MCP setup from the upgrade flow, calls out the async Request APIs codemod gap, and clarifies how to migrate or remove removed `experimental.dynamicIO` / `experimental.useCache` config. ## Why The upgrade guide should make the docs setup useful for humans and agents before migration starts, while keeping the agent prompt concise, self-contained, and grounded in the docs as the source of truth. ## Checks - `git diff --check` - MDX fence balance check - commit hook: `lint-staged` ran Prettier and ESLint on the changed MDX file
Next.js
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.