We are forced to migrate from npm to yarn: - Somehow one of our dependencies fail to install with old version of npm. - Updating npm to last version fixes thi

We are forced to migrate from npm to yarn: - Somehow one of our dependencies fail to install with old version of npm. - Updating npm to last version fixes this, but on some machines, npm install fails with a 401 error despite having no private registries configured. Still no fixes for this bug after multiples months: - https://github.com/npm/cli/issues/2799 https://github.com/npm/cli/issues/2799 - https://github.com/npm/cli/issues/3284 https://github.com/npm/cli/issues/3284 - There is a lot of other issues on this. Before this, whe had multiples other issues with npm (thats may be still live): - npm is not extensible enough and require a lot of workarounds to be used in safely CI. - There are bugs thats are not fixed for 2 years that make npm ci not working. (https://github.com/npm/cli/issues/289 https://github.com/npm/cli/issues/289) - All bug reports have been closed after a new version release because they have no idea if they fixed a bug or not.