8 ms·
All of these (except 3) also get solved by moving dependencies to a hosted npm registry. Something which has been suitable for some projects I’ve worked on. And
by korla 7y ago
All of these (except 3) also get solved by moving dependencies to a hosted npm registry. Something which has been suitable for some projects I’ve worked on. And keeps ’git clone’-times down.
- leipert 7y agoWell, not necessarily. Basically you create a new dependency and a piece of infrastructure _you_ need to maintain and that often still relies on yarn/npm upstream registries. So if that part of the infrastructure is down, you cannot work. A repo might be more error resilient, because if you check it out, you check it out.