Interactively create a package.json file

Create a package.json file with all defaults, skipping prompts

Initialize a scoped package interactively

Set default author name used during npm init

Set default author email used during npm init

Set default license used during npm init

Set the default npm registry URL

Get the currently configured npm registry URL

Remove the registry config key, reverting to default

List all active npm configuration values

List all npm config values in JSON format

Open the global .npmrc file in the default editor

Configure npm to save exact versions instead of semver ranges

Set the default semver prefix used when saving dependencies

Set an HTTP proxy for npm network requests

Set an HTTPS proxy for npm network requests

Set a custom directory for the npm cache

Install all dependencies listed in package.json

Install only production dependencies, skipping devDependencies

Install only devDependencies

Install dependencies without updating package-lock.json

Install packages ignoring peer dependency conflicts

Force reinstall of all packages, bypassing cache and lock

Install packages without running any lifecycle scripts

Use cached packages when available, falling back to network

Force network fetch even when cached packages are available

Install the latest version of the express package as a dependency

Install a specific version of the express package

Install the latest tagged version of the express package

Install express at the latest version satisfying the given semver range

Install express and explicitly add it to dependencies in package.json

Install express and pin the exact version in package.json

Install typescript as a development dependency

Install an exact version of typescript as a devDependency

Install lodash as an optional dependency

Install typescript globally on the system

Update npm itself to the latest version globally

Install multiple packages simultaneously as dependencies

Install a scoped package as a devDependency

Install a package directly from a GitHub repository URL

Install a package from a GitHub shorthand reference

Install a package from a specific branch of a GitHub repository

Install a package from a local directory path

Install a local package using the file: protocol

Install a package from a remote tarball URL

Install express without modifying package.json

Simulate installing express without making any actual changes

Install express with verbose output for debugging

Remove express from node_modules and package.json dependencies

Remove express from node_modules and explicitly remove from dependencies

Remove typescript from node_modules and devDependencies

Remove lodash from node_modules and optionalDependencies

Remove a globally installed package

Remove express from node_modules without modifying package.json

Remove multiple packages simultaneously

Update all packages to the latest version within their semver range

Update express to the latest version within its semver range

Update all packages and persist updated versions to package.json

Update all globally installed packages

Update a specific globally installed package

Update packages up to 2 levels deep in the dependency tree

Execute the build script defined in package.json scripts

Execute the dev script defined in package.json scripts

Execute the test script defined in package.json scripts

Execute the lint script defined in package.json scripts

Execute the format script defined in package.json scripts

Execute the start script defined in package.json scripts

Run the start script shorthand (no run keyword needed)

Run the test script shorthand (no run keyword needed)

Pass additional arguments to a script after the double-dash separator

Run the build script only if it exists, without erroring if absent

List environment variables available to scripts at runtime

Execute a locally installed binary from node_modules/.bin

Execute a local binary with arguments using the double-dash separator

Run a package binary without installing it permanently

Run a package binary, auto-confirming installation prompts

Run a local binary only, without fetching from registry if missing

Specify a package to install and then run its binary

Install dependencies for all workspaces in a monorepo

Install dependencies for a specific workspace by path

Run the build script across all workspaces

Run the build script in a specific workspace

Run test script across all workspaces only where it exists

Install a package into a specific workspace

Execute a binary in the context of a specific workspace

Get the name field from package.json for all workspaces

Publish the current package to the npm registry

Publish a scoped package publicly to the npm registry

Publish a package as restricted (private)

Publish the package under a custom dist-tag instead of latest

Simulate publishing without uploading anything to the registry

Publish using a one-time password for 2FA-enabled accounts

Remove a specific version of a package from the registry

Force-remove an entire package from the registry

Mark a specific package version as deprecated with a message

Add a dist-tag pointing to a specific version

Remove a dist-tag from a package

List all dist-tags for a package

Create a .tgz tarball of the current package without publishing

List files that would be included in the tarball without creating it

Log in to the npm registry interactively

Log in to a specific npm registry

Associate a scope with a specific registry and log in

Log out from the npm registry, removing auth tokens

Log out from a specific registry

Display the currently authenticated npm username

Display the authenticated username for a specific registry

List all authentication tokens for the current account

Create a new authentication token

Create a read-only authentication token

Create a token restricted to a specific CIDR IP range

Revoke a specific authentication token by its ID or value

Display metadata for the express package from the registry

Display only the latest version of express

List all published versions of express

Display the dependencies of the latest express version

Display full package metadata in JSON format

Alias for npm info — display registry metadata for a package

Show dependencies for a specific version of express

Search the npm registry for packages matching a keyword

Search the npm registry and return results as JSON

Search npm with a limit on the number of results returned

Open the documentation homepage for the express package in a browser

Open the repository URL for the express package in a browser

Open the issue tracker for the express package in a browser

Open the homepage of the express package in a browser

List installed packages and their dependency tree in the current project

List only top-level installed packages without sub-dependencies

List installed packages up to one level of sub-dependencies

Output the installed dependency tree in JSON format

List only production dependencies in the tree

List only development dependencies in the tree

Check if express is installed and show its resolved version

List all globally installed packages

List top-level globally installed packages only

List the full dependency tree including all nested dependencies

List only symlinked packages in node_modules

Scan installed dependencies for known security vulnerabilities

Output vulnerability audit results as JSON

Audit only production dependencies for vulnerabilities

Exit with error only if critical severity vulnerabilities are found

Exit with error if high or critical severity vulnerabilities are found

Exit with error if moderate or higher severity vulnerabilities are found

Automatically fix vulnerabilities by updating affected packages

Force fix vulnerabilities even if it requires breaking semver changes

Simulate audit fixes without applying any changes

Fix vulnerabilities in package-lock.json only without touching node_modules

Increment the patch version in package.json and create a git tag

Increment the minor version in package.json and create a git tag

Increment the major version in package.json and create a git tag

Increment to the next prepatch prerelease version

Increment to the next preminor prerelease version

Increment to the next premajor prerelease version

Increment the prerelease number of the current version

Increment the prerelease version with a custom identifier like alpha

Set an explicit version number in package.json

Increment the patch version without creating a git commit or tag

Increment patch version and use a custom git commit message

Clear the entire npm cache directory

Verify the integrity and consistency of the npm cache

List cached packages stored in the npm cache directory

Create a global symlink for the current package for local development

Link a globally symlinked package into the current project

Remove a previously linked package from the current project

Remove the global symlink created for the current package

Check which installed packages have newer versions available

Output outdated package information as JSON

Check outdated status for top-level packages only

Check for outdated globally installed packages

Run a set of environment checks to verify npm is configured correctly

Read the name field from the current package.json

Read the version field from the current package.json

Read all scripts defined in the current package.json

Set the name field in package.json

Set the version field in package.json

Add or update a script entry in package.json

Set the minimum required Node.js version in package.json

Remove a specific key from package.json

Install dependencies strictly from package-lock.json for reproducible CI builds

Install only production dependencies from package-lock.json

Install from lockfile without running lifecycle scripts

Install from lockfile suppressing all output except errors

Install from lockfile using cache where possible

Add a user to an npm organization with the developer role

Add a user to an npm organization with the admin role

Remove a user from an npm organization

List all members of an npm organization

Create a new team within an npm organization

Delete a team from an npm organization

Add a user to a specific team within an organization

Remove a user from a specific team within an organization

List all teams within an npm organization

List all members of a specific team within an organization

Set a package's access level to public

Set a package's access level to restricted (private)

Grant read-only access to a team for a specific package

Grant read-write access to a team for a specific package

Revoke a team's access to a specific package

List all packages accessible to an organization

List all collaborators with access to a specific package

Print the path to the local node_modules directory

Print the path to the global node_modules directory

Print the path to the local .bin executables directory

Print the path to the global bin executables directory

Print the nearest parent directory containing a package.json

Print the global npm prefix directory

Rebuild all native addons for the current Node.js version

Rebuild a specific native addon package

Reduce duplication in the dependency tree by flattening shared packages

Remove packages from node_modules that are not listed in package.json

Remove devDependency packages not needed in production

Lock down dependency versions by generating an npm-shrinkwrap.json file

Display funding information for installed packages

Display funding information for a specific package

Explain why a package is installed and which packages depend on it

Output the dependency explanation for a package as JSON

Output a shell completion script for npm commands

Open the documentation page for the npm install command

Search npm help documentation for pages related to a keyword

Display the currently installed version of npm