3 ms·
Switching to yarn is not going to fix this. However, this raise some concern about npm cli - we are relying on 2 people team for our applications. - maintainer
by tuananh 9y ago
Switching to yarn is not going to fix this. However, this raise some concern about npm cli
- we are relying on 2 people team for our applications.
- maintainer doesn't seem to care much about this horrific bug: https://imgur.com/a/v4Ndb https://imgur.com/a/v4Ndb
- rk06 9y ago> Switching to yarn is not going to fix this. Yeah, but if you had switched to yarn beforehand, then you would not be facing this issue.
- tuananh 9y agoiirc yarn has a bug regarding `which` cli which is similar to this. bugs are bound to happen and it's part of software development. however, the team size of npm cli and the way they react to this incident are what make me concern more.