Closed sladiri closed 7 years ago
yep going with npm as baseline and have yarn as an opt in sounds like a plan to me
What bugged me about Yarn a bit was, that it does not work completely with NVM. Global yarn packages are not installed separated by the NVM installations. They go to ~/.config/yarn/...
, instead of ~/.nvm/...
. There is a static setting for this path, but it is an additional thing to keep in mind (ie, change it when you change NVM version).
I added a --yarn flag like the --spa, but I am not sure how to test this change.
OK, I tested it with npm link, there was a bug of course. :)
with the new npm5 eusing yarn does not offer such huge advantages anymore. could we maybe use npm as the default packag manager and yarn as an option that you can set via cmd-line param just like --spa ?