4 ms·
This reduces package-installing friction, but this is a good thing anyway -- there's no reason why you shouldn't be able to use foobar@1.0 and foobar@2.0 in the
by zkldi 5y ago
This reduces package-installing friction, but this is a good thing anyway -- there's no reason why you shouldn't be able to use foobar@1.0 and foobar@2.0 in the same project. For all intents and purposes they're different packages, viz. the version is just as important as the package name.
- Vinnl 5y agoYeah to be clear, I wasn't trying to say it was a bad feature, just that this might be one of the negative sides part of its trade-off.