NPM Notification

[open-source-ideas]

NPM Notification

[phun-ky]

Have you tried https://doppins.com/ ? It does what you want, sort of. I understand from your spec that you want something smaller. https://gemnasium.com/ is something else, not that obtrusive, but works.

[bsonntag]

As promised, here's the code: https://github.com/bsonntag/npm-notifier

[Haroenv]

https://twitter.com/holman/status/793561589290979328 Libraries.io might have a similar feature now

[styfle]

A scenario I can envision: I get an update that Jest has a new major version released. I know this means an API breakage, so I can see the changelog and see what's changed.

For anyone else running into this problem, I have been using https://dependabot.com and it works great for notifying any changes to a package.

Any time a new version is released, it creates a PR with the following:

• Release notes from github
• CHANGELOG.md (since previous release)
• Commits (since previous release)
• Compatibility (how many others updated from previous version and tests still pass)

See an example here: styfle/packagephobia#94

[FredrikAugust]

Closing as it is fixed by @bsonntag, and any further discussion should be moved there.

[mikaelbr]

Thanks for the update! Yeah, I've seen both greenkeeper.io and doppins.com. But that's not really the same problem as this though. This is more for a person to keep updated on package/module progress, and not as much for a project to get updated to the latest version. You can call this "bigger picture stuff" in a sense.

A scenario I can envision: I get an update that Jest has a new major version released. I know this means an API breakage, so I can see the changelog and see what's changed. If there are any new features I really want I know I can update in some projects.

So it's more an immediate notification when something major happens. If that makes sense?

[brankol]

I'd be interested to work on this but I'm not sure how to go about it.
You mentioned npm hooks as a way of subscribing to changes but unless I'm missing something, there are a couple of issues there:

1. npm hooks are only available to paid users
2. there is a limit of 100 hooks per user account which might or might not be an issue depending on how many projects a user would like to track
3. you need to give a callback URI when setting up a hook and given that most people are behind dynamic IPs, one would need a dynamic dns just for this
4. if this is implemented as a hosted service, there would be a problem of running a long lived process on your computer which would listen for updates and trigger a notification

[mikaelbr]

Great! I haven't dived any deep into the new hooks API, so this might not even be possible using that. I thought that hooks would be for paid users only as a beta, but maybe I figured wrong.

If hooks aren't the way to go, maybe you could investigate doing some polling with caching. Have to confer with the licensing for NPM here, but doing something like npm show <package-name> version periodically (not too often) could be a fallback.

[bsonntag]

I've been playing around with this idea by following this guide: https://github.com/npm/registry-follower-tutorial

I have two working examples, one using node-notifier and another using Electron. I'll share the code soon.

[mikaelbr]

Cool! I get that it's probably still for experimenting and good idea to make an electron app from it. Didn't think of that 👍 I would suggest (and you are probably thinking this already) to split up the different user interfaces (electron and CLI) to two different packages both using a library for getting the data. Users interested in the CLI shouldn't have to install electron etc. But as I said, you are probably thinking this already.