npx

Download the latest version of `<pkg>` (if not in `node_modules/.bin`) and run its CLI entry, then clean up the temporary cache.

<pkg>@<version> pin; --yes / -y auto-confirm the install prompt; --package <pkg> provide a separate package to put on PATH

Pin the version used for the one-off run. The `@<version>` syntax uses semver ranges or dist-tags just like npm install.

Skip the confirmation prompt when downloading — required in CI and useful for repeatable shell scripts.

Scaffold a Vite app (Vue / React / Svelte / vanilla) — fast scaffolding that doesn't bloat your project with a CLI dependency.

--template vue | react | react-ts | svelte | lit | vanilla | etc.

Scaffold a Next.js app with the chosen router (App Router or Pages Router), TypeScript flag, ESLint, Tailwind, and `src/` placement.

--typescript; --tailwind; --eslint; --app; --src-dir; --import-alias "@/*"

Scaffold a CRA-style React app (CRA itself is in maintenance, but the binary still works for legacy projects and quick demos).

--template typescript; --use-npm | yarn | pnpm

When `<bin>` is already in the current `node_modules/.bin`, npx just executes without fetching anything. The recommended way to run locally installed dev tools.

Force npx to fail instead of fetching from the registry — useful in CI to detect missing local dependencies.

Run a binary directly from a GitHub repo's `main` branch — handy for one-off test releases.

Pin to a specific ref of a GitHub repo.

Run a script hosted as a GitHub gist. Useful for shared utilities but mind the security implications — anyone can run any gist.

Run a single JavaScript file with Node, picking up local `node_modules` for `require`/`import` resolution. Convenience over `node script.js`.

Use `tsx` (or `ts-node`) to execute a TypeScript file directly. Requires `tsx` to be locally installed.

Make extra packages available on PATH for the run. Useful when the runner depends on side dependencies that aren't directly `npm install`-ed.

Wipe the npx package cache (`~/.npm/_npx` on POSIX, `%LocalAppData%\npm-cache\_npx` on Windows) so the next run re-fetches from the registry.

-y to skip prompts; --no to test fetch

Inspect cached packages manually — each subdirectory is one resolved specifier with its own `package.json` and `node_modules`.

Force npx to fetch from the registry even if a local binary with the same name exists. Useful when you want the latest upstream release regardless of project deps.

-y accept the install prompt automatically

Set the working directory and use `<pkg>` on PATH for the single invocation. `<cmd>` runs after install completes.

Most modern scaffolds (`create-vite`, `create-next-app`, `create-nuxt-app`) auto-detect when they are launched through `npx -y` and skip the install-confirm prompt.

--typescript / --javascript / --template <name>

Override npx's auto-detection of the shell used to run scripts on Windows / unusual POSIX setups.

Skip lifecycle scripts (postinstall / preinstall) when npx installs a one-off package. Safer for unfamiliar specs.

Run a command using the latest available version of `<pkg>`, regardless of any local install.

Print the npx version (matches the bundled npm).

List every flag npx accepts.

Modern npm equivalent of `npx <pkg>`. `npm exec` accepts the same arguments and is recommended over `npx` in some npm docs, but `npx` is shorter and ubiquitous.

--package <pkg>; --yes / -y; --call=<cmd>; --workspaces