3 ms·
Kinda surprised by all the "stuck on Yarn v1" comments so far... We went through the same "~2015 everyone uses yarn", "~2020 everyone goes back to npm" cycle,
by stephen 3y ago
Kinda surprised by all the "stuck on Yarn v1" comments so far...
We went through the same "~2015 everyone uses yarn", "~2020 everyone goes back to npm" cycle, but in the last ~year or so are back on yarn v3 for...reasons that I forget (oh yeah, the ability to download multiple platform libs for when you're running in docker [1])...but :shrug: it's been great.
My only complaint is that `yarn dedupe` should be automatic (as it was in yarn v1), or at least via a flag. :-D
But otherwise yarn v3 (with the node_modules linker) has been great, and look forward to using v4.
[1] here's the "afaict npm can't do this?" snippet we use in `.yarnrc.yml`: https://gist.github.com/stephenh/43c7f15b97b73baf821f2a22c62172c7 https://gist.github.com/stephenh/43c7f15b97b73baf821f2a22c62...
- depr 3y agoSkipped v2, v3 works fine for me as well.