docs: correct dev, analyze and init command details

Author: danielroe

docs/1.overview.md

@@ -98,6 +98,6 @@ npm install -D @nuxt/cli-nightly
 npx @nuxt/cli-nightly dev
 ```
 
-`create-nuxt-nightly` scaffolds with it, and `npm create nuxt@latest --nightly` scaffolds a project against the Nuxt nightly channel.
+`create-nuxt-nightly` scaffolds with it, and `npm create nuxt@latest -- --nightly` scaffolds a project against the Nuxt nightly channel.
 
 Builds for an individual pull request are published by [pkg.pr.new](https://pkg.pr.new) and linked from the pull request itself, which is the quickest way to check whether a fix works before it is released.

docs/analyze.md

@@ -14,7 +14,7 @@ npx nuxt analyze [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>
 ```
 <!--/analyze-cmd-->
 
-The `analyze` command builds Nuxt and analyzes the production bundle (experimental). The results are served on a local server when the build finishes, unless you pass `--no-serve`.
+The `analyze` command builds Nuxt and analyzes the production bundle (experimental). The results are served on a local server when the build finishes, unless you pass `--no-serve` or `CI` is set in the environment.
 
 Routes are not prerendered while analyzing, since prerendering runs the built app and its output is not what is being measured. Pass `--prerender` if your analysis needs it.
 

docs/dev.md

@@ -14,7 +14,7 @@ npx nuxt dev [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [-
 ```
 <!--/dev-cmd-->
 
-The `dev` command starts a development server with hot module replacement at [http://localhost:3000](https://localhost:3000)
+The `dev` command starts a development server with hot module replacement at [http://localhost:3000](http://localhost:3000)
 
 ![nuxt dev](/capture/output/nuxt-dev-static.svg)
 
@@ -65,7 +65,7 @@ The `dev` command starts a development server with hot module replacement at [ht
 | `--profile=<verbose>`                |                   | Profile performance, writing a V8 CPU profile and a JSON report on exit. Use `--profile=verbose` for a full console report.                          |
 <!--/dev-opts-->
 
-The port and host can also be set via `NUXT_PORT`, `PORT`, `NUXT_HOST` or `HOST` environment variables.
+The port and host can also be set via `NUXT_PORT`, `NITRO_PORT`, `PORT`, `NUXT_HOST`, `NITRO_HOST` or `HOST` environment variables.
 
 This command sets `process.env.NODE_ENV` to `development`.
 
@@ -126,8 +126,8 @@ The build timings, `perf-report.json` and `perf-trace.json` come from Nuxt's own
 
 | Variable                  | Purpose                                                              |
 |---------------------------|----------------------------------------------------------------------|
-| `NUXT_PORT`, `PORT`       | Port to listen on                                                    |
-| `NUXT_HOST`, `HOST`       | Host to listen on                                                    |
+| `NUXT_PORT`, `NITRO_PORT`, `PORT` | Port to listen on                                            |
+| `NUXT_HOST`, `NITRO_HOST`, `HOST` | Host to listen on                                            |
 | `NUXT_TUI`                | `1` to force the interactive UI on, `plain` to opt out               |
 | `NUXT_TERM_THEME`         | `light` or `dark`, when the terminal's background cannot be detected  |
 | `NUXT_IGNORE_LOCK`        | `1` to ignore a dev server already running for this project           |

docs/init.md

@@ -57,9 +57,13 @@ The `create-nuxt` command initializes a fresh Nuxt project using [unjs/giget](ht
 Without a terminal to prompt in, the answers it would have asked for have to be passed as arguments: the directory, `--template`, `--packageManager` and `--gitInit`. Anything missing is reported along with the available templates, and the command exits with `2`.
 
 ```bash [Terminal]
-npm create nuxt@latest my-app --template minimal --packageManager pnpm --no-gitInit
+npm create nuxt@latest my-app -- --template minimal --packageManager pnpm --no-gitInit
 ```
 
+::note
+The `--` is needed with `npm create`, which reads anything flag-shaped after the initializer as npm's own config and warns `Unknown cli config` instead of passing it on. Other package managers forward the whole command line as it is, so pass the flags to them directly: `pnpm create nuxt@latest my-app --template minimal`.
+::
+
 ## Environment Variables
 
 - `NUXI_INIT_REGISTRY`: Set to a custom template registry. ([learn more](https://github.com/unjs/giget#custom-registry)).