nuxt analyze --no-serve option
The --no-serve option skips serving the analysis results. No default value is specified.
commands
101 notes in this subject, read out of this brain and free to use. This is page 1 of 2.
nuxt analyze sets NODE_ENV to production
The analyze command sets process.env.NODE_ENV to 'production'.
nuxt analyze command syntax
The nuxt analyze command builds Nuxt and analyzes the production bundle (experimental). The full command syntax is: npx nuxt analyze [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [--dotenv] [-e, --extends=<layer-name>] [--name=<name>] [--no-serve]
nuxt analyze --extends option
The -e or --extends=<layer-name> option extends from a Nuxt layer. No default value is specified.
nuxt analyze --name option
The --name=<name> option specifies the name of the analysis. Default value is 'default'.
build-module --prepare option
The --prepare option prepares the module for local development. It is a boolean flag with a default value of false.
build-module --stub option
The --stub option stubs the dist directory instead of actually building it for development. It is a boolean flag with a default value of false.
build-module --sourcemap option
The --sourcemap option generates sourcemaps for the build. It is a boolean flag with a default value of false.
nuxt build-module command signature
The nuxt build-module command has the signature: npx nuxt build-module [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [--build] [--stub] [--sourcemap] [--prepare]. It runs @nuxt/module-builder to generate a dist directory within your rootDir that contains the full build for your nuxt-module.
build-module ROOTDIR argument
The ROOTDIR argument specifies the working directory. Its default value is '.'.
build-module --cwd option
The --cwd=<directory> option specifies the working directory. This takes precedence over ROOTDIR. The default value is '.'.
build-module --logLevel option
The --logLevel=<silent|info|verbose> option specifies the build-time log level. Accepted values are 'silent', 'info', or 'verbose'. It has no default value specified.
build-module --build option
The --build option builds the module for distribution. It is a boolean flag with a default value of false.
nuxt cleanup removes these directories and caches
The cleanup command removes: .nuxt, .output, node_modules/.vite, and node_modules/.cache.
nuxt cleanup command syntax
The cleanup command is invoked with the syntax: npx nuxt cleanup [ROOTDIR] [--cwd=<directory>]. It removes common generated Nuxt files and caches.
nuxt build --preset option
The --preset=<preset> option specifies the Nitro server preset for the nuxt build command. Available presets depend on Nitro and include examples like 'node-server', 'vercel', 'netlify', and 'static'.
nuxt build command syntax
The nuxt build command creates a .output directory with all your application, server and dependencies ready for production. Syntax: npx nuxt build [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [--prerender] [--preset] [--dotenv] [--envName] [-e, --extends=<layer-name>] [--profile[=verbose]]
nuxt build ROOTDIR argument
The ROOTDIR argument specifies the working directory for the nuxt build command. The default value is '.'
nuxt build --cwd option
The --cwd=<directory> option specifies the working directory for the nuxt build command. This takes precedence over ROOTDIR. Default is '.'
nuxt build --prerender option
The --prerender option builds Nuxt and prerenders static routes. When --prerender is used, it always sets the preset to 'static'.
nuxt build --dotenv option
The --dotenv option specifies the path to a .env file to load, relative to the root directory, for the nuxt build command.
nuxt build sets NODE_ENV to production
The nuxt build command sets process.env.NODE_ENV to 'production'.
nuxt devtools command syntax
The nuxt devtools command allows you to enable or disable Nuxt DevTools on a per-project basis. The command syntax is: npx nuxt devtools <COMMAND> [ROOTDIR] [--cwd=<directory>]
nuxt devtools enable functionality
Running 'nuxt devtools enable' installs Nuxt DevTools globally and enables it within the particular project. The setting is saved as a preference in the user-level .nuxtrc file.
nuxt devtools disable functionality
Running 'nuxt devtools disable' removes devtools support for a particular project.
nuxt devtools command arguments
The nuxt devtools command accepts the following arguments: COMMAND (required, options: enable or disable - the command to run), ROOTDIR (optional, default: '.' - specifies the working directory).
nuxt devtools command options
The nuxt devtools command accepts the following option: --cwd=<directory> (optional, default: '.' - specifies the working directory and takes precedence over ROOTDIR).
nuxt dev ROOTDIR argument
The ROOTDIR argument specifies the working directory for nuxt dev. Default value is "." (current directory).
nuxt dev port and host environment variables
The port and host for nuxt dev can be set via environment variables: NUXT_PORT, PORT, NUXT_HOST, or HOST.
nuxt dev options reference
The nuxt dev command accepts the following options: --cwd=<directory> (specify working directory, takes precedence over ROOTDIR, default: "."), --logLevel=<silent|info|verbose> (specify build-time log level), --dotenv (path to .env file to load, relative to root directory), --envName (environment to use when resolving configuration overrides, default is "production" when building and "development" when running dev server), -e/--extends=<layer-name> (extend from a Nuxt layer), --clear (clear console on restart, default: false), --no-f/--no-fork (disable forked mode), -p/--port (port to listen on, default: NUXT_PORT || NITRO_PORT || PORT || nuxtOptions.devServer.port), -h/--host (host to listen on, default: NUXT_HOST || NITRO_HOST || HOST || nuxtOptions.devServer?.host), --clipboard (copy URL to clipboard, default: false), -o/--open (open URL in browser, default: false), --https (enable HTTPS), --publicURL (displayed public URL used for QR code), --qr (display QR code of public URL when available), --public (listen to all network interfaces), --tunnel (open a tunnel using https://github.com/unjs/untun), --profile (profile performance, writes V8 CPU profile and JSON report on exit, use --profile=verbose for full console report), --sslCert (deprecated, use --https.cert instead), --sslKey (deprecated, use --https.key instead).
nuxt dev NODE_ENV environment variable
The nuxt dev command sets process.env.NODE_ENV to "development".
nuxt dev listhen options pass-through
The @nuxt/cli can pass options through to listhen, such as --no-qr to turn off the dev server QR code. Additional listhen options are available and documented in the unjs/listhen repository.
nuxt dev self-signed certificate configuration
When using a self-signed certificate in development with nuxt dev, set NODE_TLS_REJECT_UNAUTHORIZED=0 in the environment.
nuxt dev command syntax
The nuxt dev command starts a development server with hot module replacement at http://localhost:3000. Full syntax is: npx nuxt dev [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [--dotenv] [--envName] [-e, --extends=<layer-name>] [--clear] [--no-f, --no-fork] [-p, --port] [-h, --host] [--clipboard] [-o, --open] [--https] [--publicURL] [--qr] [--public] [--tunnel] [--profile[=verbose]] [--sslCert] [--sslKey]
nuxt generate --extends option
-e, --extends=<layer-name> extends from a Nuxt layer. No default is specified in the documentation.
nuxt generate --profile option
--profile profiles performance and writes a V8 CPU profile and JSON report on exit. Use --profile=verbose for a full console report. This option is available from v4.4 onwards. No default is specified in the documentation.
nuxt generate command signature
The nuxt generate command pre-renders every route of your application and stores the result in plain HTML files that can be deployed on any static hosting services. The command triggers the nuxt build command with the prerender argument set to true. The full command signature is: npx nuxt generate [ROOTDIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [--preset] [--dotenv] [--envName] [-e, --extends=<layer-name>] [--profile[=verbose]]
nuxt generate ROOTDIR argument
ROOTDIR is an optional argument that specifies the working directory for the generate command. The default value is '.' (current directory).
nuxt generate --preset option
--preset specifies the Nitro server preset. No default value is specified in the documentation.
nuxt info command signature
The nuxt info command logs information about the current or specified Nuxt project. The command signature is: npx nuxt info [ROOTDIR] [--cwd=<directory>]
nuxt info command ROOTDIR argument
The info command accepts a ROOTDIR argument that specifies the working directory. The default value is '.'.
nuxt info command --cwd option
The info command accepts a --cwd=<directory> option to specify the working directory. This option takes precedence over ROOTDIR. The default value is '.'.
create nuxt --nightly option
The --nightly option uses the Nuxt nightly release channel (3x or latest) with no default value.
npm create nuxt command syntax
The command to initialize a fresh Nuxt project is `npm create nuxt@latest [DIR] [--cwd=<directory>] [--logLevel=<silent|info|verbose>] [-t, --template] [-f, --force] [--offline] [--preferOffline] [--no-install] [--gitInit] [--shell] [--packageManager] [-M, --modules] [--no-modules] [--nightly]`. It uses unjs/giget to initialize projects.
create nuxt DIR argument
The DIR argument specifies the project directory and has an empty string as default value.
create nuxt --cwd option
The --cwd=<directory> option specifies the working directory and defaults to `.`
create nuxt --template option
The -t, --template option specifies a template name with no default value.
create nuxt --force option
The -f, --force option overrides an existing directory with no default value.
create nuxt --offline option
The --offline option forces offline mode with no default value.
create nuxt --preferOffline option
The --preferOffline option prefers offline mode with no default value.
create nuxt --no-install option
The --no-install option skips installing dependencies with no default value.
create nuxt --gitInit option
The --gitInit option initializes a git repository with no default value.
create nuxt --shell option
The --shell option starts a shell after installation in the project directory with no default value.
create nuxt --packageManager option
The --packageManager option specifies package manager choice (npm, pnpm, yarn, bun) with no default value.
create nuxt --modules option
The -M, --modules option specifies Nuxt modules to install as comma separated values without spaces, with no default value.
create nuxt --no-modules option
The --no-modules option skips the module installation prompt with no default value.
NUXI_INIT_REGISTRY environment variable
The NUXI_INIT_REGISTRY environment variable can be set to a custom template registry. The default registry is loaded from https://github.com/nuxt/starter/tree/templates/templates.
nuxt module search command syntax
The `nuxt module search` command searches for Nuxt modules matching your query that are compatible with your Nuxt version. Syntax: `npx nuxt module search <QUERY> [--cwd=<directory>] [--nuxtVersion=<2|3>]`.
nuxt module search example
To search for Nuxt modules with the keyword 'pinia', run: `npx nuxt module search pinia`
nuxt module search options
The `nuxt module search` command accepts the following options: `--cwd=<directory>` (default: `.`) to specify the working directory, and `--nuxtVersion=<2|3>` to filter by Nuxt version and list compatible modules only (auto detected by default).