Unverified Commit 5ee8c4bd authored by Sam Ko's avatar Sam Ko Committed by GitHub

docs(cli): re-order profile to match help output (#64267)

## Why?

Forgot to add this change in here →
https://github.com/vercel/next.js/pull/64264.

Closes NEXT-3055
parent 5e7e4bc0
...@@ -191,16 +191,6 @@ Options: ...@@ -191,16 +191,6 @@ Options:
-h, --help Displays this message. -h, --help Displays this message.
``` ```
### Profiling
You can enable production profiling for React with the `--profile` flag in `next build`.
```bash filename="Terminal"
next build --profile
```
After that, you can use the profiler in the same way as you would in development.
### Debug ### Debug
You can enable more verbose build output with the `--debug` flag in `next build`. You can enable more verbose build output with the `--debug` flag in `next build`.
...@@ -229,6 +219,16 @@ next build --no-mangling ...@@ -229,6 +219,16 @@ next build --no-mangling
> **Good to know**: This may affect performance and should only be used for debugging purposes. > **Good to know**: This may affect performance and should only be used for debugging purposes.
### Profiling
You can enable production profiling for React with the `--profile` flag in `next build`.
```bash filename="Terminal"
next build --profile
```
After that, you can use the profiler in the same way as you would in development.
## Production ## Production
`next start` starts the application in production mode. The application should be compiled with [`next build`](#build) first. `next start` starts the application in production mode. The application should be compiled with [`next build`](#build) first.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment