npm hook ls [pkg]
npm hook add <entity> <url> <secret>
npm hook update <id> <url> [secret]
npm hook rm <id>Add a hook to watch a package for changes:
$ npm hook add lodash https://example.com/ my-shared-secretAdd a hook to watch packages belonging to the user substack:
$ npm hook add ~substack https://example.com/ my-shared-secretAdd a hook to watch packages in the scope @npm
$ npm hook add @npm https://example.com/ my-shared-secretList all your active hooks:
$ npm hook lsList your active hooks for the lodash package:
$ npm hook ls lodashUpdate an existing hook's url:
$ npm hook update id-deadbeef https://my-new-website.here/Remove a hook:
$ npm hook rm id-deadbeefAllows you to manage npm hooks, including adding, removing, listing, and updating.
Hooks allow you to configure URL endpoints that will be notified whenever a change happens to any of the supported entity types. Three different types of entities can be watched by hooks: packages, owners, and scopes.
To create a package hook, simply reference the package name.
To create an owner hook, prefix the owner name with ~ (as in, ~youruser).
To create a scope hook, prefix the scope name with @ (as in, @yourscope).
The hook id used by update and rm are the IDs listed in npm hook ls for
that particular hook.
The shared secret will be sent along to the URL endpoint so you can verify the request came from your own configured hook.
👀 Found a typo? Let us know!
The current stable version of npm is here. To upgrade, run: npm install npm@latest -g
To report bugs or submit feature requests for the docs, or for any issues regarding the npm command line tool, please post on the npm/cli GitHub project.