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.
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.
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.
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.
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.
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.