Other popular posts
If you use
npm then you know the frustration in keeping up to date with the particular modules you use. Whether its an API change, or just a patch fix, you want to stay informed. Well, look no further!
We are proud to introduce the newest feature for our private npm customers, npm package notifications. This is just one of the many new features we have been hard at work on since we open sourced all of our work for the community with browsenpm.org back in April.
Notifications give you a simple mechanism to stay up to date and provide a direct link to view the package and its dependencies.
- Seamlessly subscribe to either public and private packages
- Notifications via Slack, HipChat or webhooks (yes!)
- More complex notifications coming soon (conditionals, dependent updates, semver matching, etc.)
Optimizing asynchronous communication
Communication overhead can be huge when working with a distributed team. At Nodejitsu, we have developed a culture around the ability to asynchronously communicate. While chat applications like Slack and HipChat have been able to provide an efficient communication medium, you might not remember to tell a co-worker you pushed a new release they have been waiting for. Notifications automate this process for you. By subscribing to both private and public modules that are relevant to your progress, you will always stay up to date. The best part is that notifications hook right into the chat applications you are used to.
While notifications are great for your favorite chat application, they can also be used to create more automated systems! While we innately supporting Slack and HipChat integrations as targets, we also provide output specifically for WebHooks! This allows you to build systems around your publishes with ease. Want to trigger a build or even a deploy when a new version is published? It's as simple as specifying a
test target in the UI to hit your webservice.
Give it a try!
So if you've been waiting with baited breath for your co-worker to publish a new version of a module you are using, head over to the UI and subscribe to the package. You'll be the first to know, and you won't have to say "...and I had hear it from strangers?!"
Not a private npm user yet? Check out the goodness by signing up here.