3 ms·
> - Messing up certain cases of dependency resolution such that you'd get a different version than NPM would give you. NPM can mess up it's own dependencies, o
by leshow 7y ago
> - Messing up certain cases of dependency resolution such that you'd get a different version than NPM would give you.
NPM can mess up it's own dependencies, or give you different dependencies on different machines. It's algorithm is (was?) non-deterministic.
> - Local package problems of several sorts
I use yarn with lerna to keep a monorepo of local packages together, it works pretty well. At the time, npm didn't.
> - All of the above and more sometimes causing a dependency that worked under npm to fail with misleading error messages due to bad interactions between that package and yarn.
Never ran into anything like this. Show me a package that doesn't work with yarn
Yarn gave npm some much needed competition and made npm improve a bit. Before yarn, npm didn't even have lockfiles. Having both is good, but I've just had less issues with yarn overall.
- shantly 7y ago> Never ran into anything like this. Show me a package that doesn't work with yarn Been too long, don't remember. Happened more than once. Options were "debug package under yarn, and assuming there's a way to fix it without modifying yarn itself, submit PR to package's repo" or "just use npm". Naïve search for 'is:issue is:open "npm works"' over yarn's ~2,000 open issues reveals some packages that don't work with it, pretty quickly. I'm sure npm has bugs too but we consistently and reliably ran into yarn problems that could be fixed immediately by switching to npm, on several projects. A browse through their issues more generally reveal tons and tons of broken features and edge cases, still, looks like, which is how it was back when I was using it, too. If it's working for folks that's fine, but I think it's still a bad idea to give (especially) newbies the impression yarn's clearly the best choice.