4 ms·
As much as I leaned toward the merger (running both in production sucks) I don't think people thought he was being serious--obviously he had to know what io.js
by mattkrea 11y ago
As much as I leaned toward the merger (running both in production sucks) I don't think people thought he was being serious--obviously he had to know what io.js was. Instead of being humorous it comes off as somewhat smug and ignoring a legitimate question or at least that's how I took it.
- jessaustin 11y ago...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?
- mattkrea 11y agoI 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.
- netcraft 11y agoHave we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.
- mariusc23 11y agoLooks like they support up to 0.12.4 now. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html#concepts.platforms.nodejs https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...
- mattkrea 11y agoGood catch. The AMI I'm using could be outdated. I'll have to update later.
- pmalynin 11y agoI 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.