Next.js
Next.js is a framework built on React. It adds routing, server and browser rendering, data loading, asset optimization, and deployment rules.
Another example
A catalog renders product details on the server and comparison controls in the browser. Inventory revalidates without rebuilding every page.
Main parts
- 01Code or behavior under test
- 02Observable evidence
- 03Coverage, failure, and recovery
Use it when
Use it for React products needing built-in routing and mixed rendering. The team must understand caching and runtimes.
Do not use it when
Do not make everything client-side or trust hidden cache behavior. Simple static pages may not need Next.js.
Name used in code
App Router + Server Components + route handlers Before you ship
Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.
Outcome: Use or review Next.js as a technical building block that the team can maintain. User context: A catalog renders product details on the server and comparison controls in the browser. Inventory revalidates without rebuilding every page. Technology or engineering concept: Next.js. Why it fits: Use it for React products needing built-in routing and mixed rendering. The team must understand caching and runtimes. Do not use it when: Do not make everything client-side or trust hidden cache behavior. Simple static pages may not need Next.js. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.
Check this request
Review the current use of Next.js. Definition: Next.js is a framework built on React. It adds routing, server and browser rendering, data loading, asset optimization, and deployment rules. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.