Skip to content
npm package executor
JavaScript Makefile
Branch: latest
Clone or download
Latest commit 43d68c8 Aug 21, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin fix(license): change npx license to ISC Mar 8, 2018
locales fix(i18n): fix korean; 쉘 -> 셸 (#163) Apr 12, 2018
test fix: spurious test failure Aug 21, 2019
.gitignore misc: adding license and changelog Jul 11, 2017
.travis.yml travis: only test on supported node versions Jul 16, 2019 chore(release): 10.2.0 Apr 13, 2018 docs(coc): updated May 28, 2017 docs(contributing): updated May 28, 2017
ISSUE_TEMPLATE misc: add base project files May 28, 2017 fix(license): change npx license to ISC Mar 8, 2018
Makefile build: use npx in Makefile itself Jul 21, 2017
PULL_REQUEST_TEMPLATE misc: add base project files May 28, 2017 docs: Add running specific node version to examples (#129) Dec 2, 2017
appveyor.yml fix(platform): drop node 4 and 7, add 9 and 10 May 3, 2018
auto-fallback.js fix(auto-fallback): fix syntax error in bash/zsh auto-fallback Jul 11, 2017
child.js fix(standard): get things in line with standard 11 Mar 8, 2018
get-prefix.js fix(standard): get things in line with standard 11 Mar 8, 2018
index.js fix(spawn): spawn child processes with node without relying on the sh… Apr 13, 2018
package-lock.json chore(release): 10.2.0 Apr 13, 2018
package.json chore(release): 10.2.0 Apr 13, 2018
parse-args.js feat(spawn): add --always-spawn to opt out of process takeover optimi… Apr 12, 2018
util.js test: 100% coverage for get-prefix and util Jun 23, 2017
y.js fix(i18n): Y utility was ignoring falsy entries Jun 17, 2017

npm license Travis AppVeyor Coverage Status

npx(1) -- execute npm package binaries


npx [options] <command>[@version] [command-arg]...

npx [options] [-p|--package <pkg>]... <command> [command-arg]...

npx [options] -c '<command-string>'

npx --shell-auto-fallback [shell]


npm install -g npx


Executes <command> either from a local node_modules/.bin, or from a central cache, installing any packages needed in order for <command> to run.

By default, npx will check whether <command> exists in $PATH, or in the local project binaries, and execute that. If <command> is not found, it will be installed prior to execution.

Unless a --package option is specified, npx will try to guess the name of the binary to invoke depending on the specifier provided. All package specifiers understood by npm may be used with npx, including git specifiers, remote tarballs, local directories, or scoped packages.

If a full specifier is included, or if --package is used, npx will always use a freshly-installed, temporary version of the package. This can also be forced with the --ignore-existing flag.

  • -p, --package <package> - define the package to be installed. This defaults to the value of <command>. This is only needed for packages with multiple binaries if you want to call one of the other executables, or where the binary name does not match the package name. If this option is provided <command> will be executed as-is, without interpreting @version if it's there. Multiple --package options may be provided, and all the packages specified will be installed.

  • --no-install - If passed to npx, it will only try to run <command> if it already exists in the current path or in $prefix/node_modules/.bin. It won't try to install missing commands.

  • --cache <path> - set the location of the npm cache. Defaults to npm's own cache settings.

  • --userconfig <path> - path to the user configuration file to pass to npm. Defaults to whatever npm's current default is.

  • -c <string> - Execute <string> inside an npm run-script-like shell environment, with all the usual environment variables available. Only the first item in <string> will be automatically used as <command>. Any others must use -p.

  • --shell <string> - The shell to invoke the command with, if any.

  • --shell-auto-fallback [<shell>] - Generates shell code to override your shell's "command not found" handler with one that calls npx. Tries to figure out your shell, or you can pass its name (either bash, fish, or zsh) as an option. See below for how to install.

  • --ignore-existing - If this flag is set, npx will not look in $PATH, or in the current package's node_modules/.bin for an existing version before deciding whether to install. Binaries in those paths will still be available for execution, but will be shadowed by any packages requested by this install.

  • -q, --quiet - Suppressed any output from npx itself (progress bars, error messages, install reports). Subcommand output itself will not be silenced.

  • -n, --node-arg - Extra node argument to supply to node when binary is a node script. You can supply this option multiple times to add more arguments.

  • -v, --version - Show the current npx version.


Running a project-local bin

$ npm i -D webpack
$ npx webpack ...

One-off invocation without local installation

$ npm rm webpack
$ npx webpack -- ...
$ cat package.json
...webpack not in "devDependencies"...

Invoking a command from a github repository

$ npx github:piuccio/cowsay
$ npx git+ssh://my.hosted.git:cowsay.git#semver:^1

Execute a full shell command using one npx call w/ multiple packages

$ npx -p lolcatjs -p cowsay -c \
  'echo "$npm_package_name@$npm_package_version" | cowsay | lolcatjs'
< your-cool-package@1.2.3 >
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Run node binary with --inspect

$ npx --node-arg=--inspect cowsay
Debugger listening on ws://

Specify a node version to run npm scripts (or anything else!)

npx -p node@8 npm run build


You can configure npx to run as your default fallback command when you type something in the command line with an @ but the command is not found. This includes installing packages that were not found in the local prefix either.

For example:

$ npm@4 --version
(stderr) npm@4 not found. Trying with npx...
$ asdfasdfasf
zsh: command not found: asfdasdfasdf

Currently, zsh, bash (>= 4), and fish are supported. You can access these completion scripts using npx --shell-auto-fallback <shell>.

To install permanently, add the relevant line below to your ~/.bashrc, ~/.zshrc, ~/.config/fish/, or as needed. To install just for the shell session, simply run the line.

You can optionally pass through --no-install when generating the fallback to prevent it from installing packages if the command is missing.

For bash@>=4:

$ source <(npx --shell-auto-fallback bash)

For zsh:

$ source <(npx --shell-auto-fallback zsh)

For fish:

$ source (npx --shell-auto-fallback fish | psub)


Huge thanks to Kwyn Meagher for generously donating the package name in the main npm registry. Previously npx was used for a Tessel board Neopixels library, which can now be found under npx-tessel.


Written by Kat Marchan.


Please file any relevant issues on Github.


This work is released by its authors into the public domain under CC0-1.0. See for details.


  • npm(1)
  • npm-run-script(1)
  • npm-config(7)
You can’t perform that action at this time.