The npm community forum has been discontinued.
To discuss usage of npm, visit the GitHub Support Community.
NPM hooks package:change prioritized over package:publish
What I Wanted to Do
Have a consistent NPM webhook for
I have a webhook listening and handling
package:publish events. It works well. However, I noticed in some cases when you update other fields in the package.json of the published package this event is never emitted. Another
package:change is emitted instead (with empty changes, by the way).
I’d like ALL NPM registry publishes to trigger a
package:publish event, regardless of what changed. Whether or not you trigger a separate
package:change event does not bother me.
What Happened Instead
I got a
package:change when a new package version was published, but not a
- Setup webhook for a particular package.
keywordsfor said package.
- NPM publish it.
- See event name: