News for hackers. Stuff that matters.
Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by leokun on Wednesday December 04, 2013 @02:06PM (#6849270)
I'm sorry, it is over the top, I'm just so tired of npm libraries I depend on going dark or changing things without updating the version.
Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by Q_the_Novice on Wednesday December 04, 2013 @02:50PM (#6849634)
FIY, npm does not allow you to push a module version more than once.
Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by leokun on Wednesday December 04, 2013 @03:05PM (#6849746)
Pretty sure dependencies can come straight from a git url, bypassing npm. Put something on npm, and in your package.json you can depend on something straight up from github. npm will install and build that and it may break your stuff, it's a gamble. Given how dependencies nest into a massive web, you don't have to use many things before you end up with something that breaks you.
Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by elliotf on Wednesday December 04, 2013 @05:36PM (#6850931)
I think you're looking for npm shrinkwrap:

https://npmjs.org/doc/cli/npm-shrinkwrap.html

It locks in all dependencies, including dependencies of dependencies, and turtles all the way down.

Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by Touche on Wednesday December 04, 2013 @05:48PM (#6851037)
shrinkwrap just locks down a version of a dependency, if the dependency points to a git master branch, that's not locked down. shrinkwrap doesn't install any code. I think his point is valid, although also probably still very rare.
Re:Play, Scala, and Iteratees vs. Node.js and Socket.io by elliotf on Wednesday December 04, 2013 @06:12PM (#6851185)
npm will translate the git branch to its commit sha when you `npm shrinkwrap` so you're pretty well covered.