News for hackers. Stuff that matters.
Re:Introducing hooks: get notifications of npm registry and ... by xg15 on Wednesday June 01, 2016 @02:36PM (#11816981)
> You can use hooks to trigger integration testing, trigger a deploy, make an announcement in a chat channel, or trigger an update of your own packages.

(emphasis mine)

I'm not very experienced in node.js development, but wouldn't automated deployment whenever a dependency changes be a really bad idea? Especially considering the issues with dependencies breaking in npm from the not-so-distant past.

Re:Introducing hooks: get notifications of npm registry and ... by dragonwriter on Wednesday June 01, 2016 @02:40PM (#11817018)
> I'm not very experienced in node.js development, but wouldn't automated deployment whenever a dependency changes be a really bad idea?

Presumably, you'd want to trigger testing and then a deploy, rather than just triggering a deploy, but if you have fully-automated testing, there's no reason not to include a deploy after testing as part of your triggered action.

You could, if you don't have fully automated testing, trigger a deploy to a non-production server automatically, and then after whatever manual validation you do on that server, manually deploy to production.

So, there's probably use cases for triggered deploys, but you don't want to do it willy-nilly.

Re:Introducing hooks: get notifications of npm registry and ... by eknkc on Wednesday June 01, 2016 @02:40PM (#11817024)
Even with an extensive test suite I would not be comfortable automating public dep updates.

But, I guess you could set up a whitelist for internal modules that your own org manages to propogate uptades up to deployment.

Re:Introducing hooks: get notifications of npm registry and ... by ag_dubs on Wednesday June 01, 2016 @02:39PM (#11817010)
this would primarily be for people who use their own internal packages in developing their own applications, i.e. a single author owns both packages.

that being said, it turns out that the semver handshake the community does works Most of The Time, so if it is a trusted dependency it wouldn't be that dangerous. assuming you also had tests-dependent deploy, the tests would catch the break.