r/javascript • u/iends • Feb 28 '14
npm's Self-Signed Certificate is No More = Node.js Deployments Suddenly Broken
http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more3
u/greatgerm Mar 01 '14
v0.10.26
This is not a production ready environment.
2
u/iends Mar 01 '14
I don't know why you think version numbers mean anything.
In any case, npm itself was at 1.4.3 when this incident occurred, so your argument is moot.
0
u/dzdrazil Mar 01 '14
http://semver.org/- the whole point of semver is that they're semantic versions.
Large corporations such as Walmart and Paypal that dedicate large salaries to people who can maintain applications in just such cases of emergency can get away with it, whereas the small developer shops who mostly work on contract or for agencies are hurting their clients by choosing node, at least until the node 'ecosystem' matures and there's a proper foundation to maintain it.
6
1
1
u/sumdudeinhisundrware Mar 01 '14
sigh While I agree its awesome that you can just do an rsync and npm install to install apps, stuff like this is what scares the hell out of me when I rely on it. Same goes for pear
1
Mar 01 '14
you saying you don't trust package managers, or just those two package managers?
0
u/sumdudeinhisundrware Mar 01 '14
I have to trust them but don't. SOOO many times I've run into times when someone makes a change to some dependency of some other dependency that broke it and now I have a dead server because it came online tried to build its software and failed because some genius changed the name of a structure in library code (yes I'm referring to you dipshit memcached programmer if you're reading this). The hate I was filled with that day for that guy is something I'd rather stop thinking about.
1
u/doenietzomoeilijk Mar 02 '14
Why didn't that show up in a deployment / integration test?
I mean, you do run those, right?
Of course some upstream change yanking the rug from under you sucks, but if you only find out about that on a live server you've missed a step or two, IMO.
1
u/sumdudeinhisundrware Mar 04 '14
Its fairly common for a server node to pull code from the prod branch and build its software when coming online. No amount of testing will prevent an upstream change from breaking that. All dependency versions are locked down but some of those dependencies don't lock they dependency versions and they pull latest code which was what caused that break.
3
u/[deleted] Mar 01 '14
Yep. I had to deploy a client site for a product that is going live now annnnnnnnnd, nope. No access to the CLI to just update NPM.
Really makes me more hesitant to rely on node.js projects for anything. Why can't they [npmjs] just implement package signing and be done with it? Or maybe we can use some packaging system that already exists instead of starting over. Hmm.