Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes Current Release Line

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Tuesday October 31, 2017 @04:08PM (#15596127)

In my experience that’s simply not true.

We’ve seen more issues with Yarn in CI & prod than with npm 5.x

Both are great projects but npm is significantly more mature.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by saas_co_de on Tuesday October 31, 2017 @04:49PM (#15596414)

I guess it just depends on what you are doing. With npm 5.x installed packages started disappearing at random for me. Switched to yarn and no problems since.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Tuesday October 31, 2017 @06:20PM (#15597100)

I have never seen that (or even heard of it). How bizarre.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by nfriedly on Wednesday November 01, 2017 @07:20AM (#15600225)

I've had it happen to me before. It's weird and annoying, and you basically have to nuke node_modules and sometimes package-lock.json, and then re-install everything to fix. That usually works.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by nailer on Tuesday October 31, 2017 @06:45PM (#15597304)

https://github.com/npm/npm/issues/17929 and linked bugs.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by mtphil on Tuesday October 31, 2017 @04:48PM (#15596406)

Just out of curiosity, having never encountered any issues myself - what sort of issues have you run into with Yarn in CI/prod ?

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Tuesday October 31, 2017 @06:22PM (#15597110)

Reliability, mostly. Also some strange cases where it would just plain fail (but then work if re-run).

We do use private scoped packages a lot so that might have some bearing on it.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by nailer on Tuesday October 31, 2017 @06:45PM (#15597302)

I use private scoped packages (and monorepos, and yarn) too, and have generally had a fine time with it.

Would be interested in specifics of your reliability and failure problems too.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by qudat on Wednesday November 01, 2017 @01:09AM (#15598909)

We just started using yarn workspaces and are running into weird issues where our private scoped packages don't always get installed on `yarn install`.

Yarn claims to be deterministic but I still need to `rm -rf node_modules` regularly when I run into weird build errors. It's quite strange.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Wednesday November 01, 2017 @04:08AM (#15599522)

Well... I don’t use it anymore because frankly, there’s no need.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by jsight on Tuesday October 31, 2017 @10:13PM (#15598414)

Is there any chance that you are using npm to install yarn?

I had mistakenly setup our CI to do that at one point and it caused a lot of hard to debug problems.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Thursday November 02, 2017 @01:18PM (#15612305)

I was not, but even if I was that speaks to Yarn’s quality imo because they recommend that as an option.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by jhgaylor on Tuesday October 31, 2017 @04:25PM (#15596248)

We finally got NPM out of the loop for production deploys and it's been glorious. We ship down a tarball of the repo after an npm install and include a node interpreter.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Tuesday October 31, 2017 @06:20PM (#15597091)

Ah well, that’s a whole different kind of system. Similar to doing a docker image ship.

Still have to do the install on a deploy server.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by tuananh on Wednesday November 01, 2017 @01:41AM (#15599025)

seems like a perfect use case for Docker.

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by jhgaylor on Wednesday November 01, 2017 @10:57AM (#15601688)

I whole heartedly agree. Would you tell that to my boss? :D

[ Parent | on HN ]

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by rawrmaan on Tuesday October 31, 2017 @04:20PM (#15596211)

Agreed. I tried to switch to yarn a couple times now and it simply wasn't reliable (though the last attempt was a few months ago)

[ Parent | on HN ]