Prepare a bug report
A production or development bug needs an environment report that maintainers can reproduce.
Next.js 16+ · Command
next info
next info prints system, toolchain, dependency, and Next.js configuration details for diagnosing issues and preparing bug reports. Use --verbose for additional debugging information.
How it works
The command inspects the current system and Next.js project, then prints environment details useful for reporting bugs. With --verbose, it gathers additional debugging information, including more details about the installation and related packages.
Syntax
next info [--verbose]Parameters
| Name | Type | Description |
|---|---|---|
--verbose | boolean | Optional flag that collects additional debugging information. |
-h, --help | flag | Optional alias that displays command help. |
Returns
Writes diagnostic information about the current system, installed binaries and package versions, and Next.js configuration to the terminal.
Key points
- Use
next infoto produce a reproducible environment snapshot for a Next.js bug report. - The report identifies the operating system and architecture, then lists installed JavaScript package-manager binaries.
- It includes core framework and React package versions, helping maintainers detect compatibility or dependency mismatches.
- Adding
--verboseexpands the report for deeper troubleshooting.
Common mistakes
- The command is intended for diagnostics and bug reports, not for building, serving, or modifying the application.
- Use --verbose when the basic report is insufficient, especially for installation or dependency diagnosis.
Example: Collect verbose environment information
next info --verboseRun this from the project root when a bug report or installation diagnosis needs more detailed environment and package information.
When to use it
Diagnose installation issues
An installation problem may involve mismatched Node, package-manager, React, or Next.js versions.
Audit project diagnostics
A project’s local configuration and dependency context need to be inspected from the terminal.
Interview questions
QWhat does next info do?
next info prints diagnostic details about the current system and project. Its report includes the operating-system platform, architecture and version, available binaries, relevant package versions, and Next.js configuration.
Follow-up: What should be added when the normal report lacks enough installation detail? Run next info --verbose to collect additional debugging information about the installation and related packages.
QHow would you use next info in a bug report?
Run next info from the project's root directory. The resulting report can be included with a GitHub issue so maintainers can inspect the environment and dependency versions.
Follow-up: Why does the project root matter? It lets the command inspect the local Next.js project and its installed package context rather than only the host machine.
QWhat information does the command collect?
The command reports versions for tools such as Node.js, npm, Yarn, and pnpm, along with packages including next, react, and react-dom. It also reports operating-system information and Next.js configuration.
Follow-up: Which option increases diagnostic coverage? --verbose requests additional debugging information beyond the standard environment summary.
Related
nextnext devnext buildnext start