One Year with Node.js

Re:One Year with Node.js by jessaustin on Tuesday June 16, 2015 @07:47PM (#9729356)

...running both in production sucks...

I'm sure it does. Can you describe the situation that has forced you to do this? Do you rely on modules that are limited to one or the other? Are those internal modules?

[ Parent | on HN ]

Re:One Year with Node.js by mattkrea on Tuesday June 16, 2015 @07:59PM (#9729387)

I simply haven't had the time to upgrade some but others are running on Elastic Beanstalk which is capped at Node 0.10.26 believe it or not.

For newer things I'm running io.js 2.x and patiently waiting for the first merged release but wanted io.js for the ES6 functionality and IIRC Node 0.12.0 wasn't out yet.

[ Parent | on HN ]

Re:One Year with Node.js by mariusc23 on Tuesday June 16, 2015 @10:08PM (#9729756)

Looks like they support up to 0.12.4 now.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...

[ Parent | on HN ]

Re:One Year with Node.js by mattkrea on Tuesday June 16, 2015 @10:38PM (#9729818)

Good catch. The AMI I'm using could be outdated. I'll have to update later.

[ Parent | on HN ]

Re:One Year with Node.js by netcraft on Tuesday June 16, 2015 @08:39PM (#9729512)

Have we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.

[ Parent | on HN ]

Re:One Year with Node.js by pmalynin on Tuesday June 16, 2015 @08:29PM (#9729473)

I had a problem where fibers was working on v0.12.3 with two applications, and when I deployed a third one with the regular "npm install && forever start" deal I got a "package did not self-register" issue that was only solved by rolling back to v0.10.36.

[ Parent | on HN ]