SebastianVerified account

agree, hyping is not the goal. It is fascinating since it is pretty much counter to all other modern projects. The delta here is worth thinking about.

Like anything it's a trade-off. In the case of build-time tools like Svelte and Rollup I think it's worthwhile, because faster installation time and guarantee of no version mismatch bugs far outweighs saving a few kb inside node_modules

Isn’t that why locked dep versions exist? E.g. package-lock.json

All well and good if all your dependencies have lockfiles for the package manager you happen to use. Regardless, lockfiles only solve the reproducible builds problem; they don't solve the fact that installing tons of dependencies is slow

Also flaky - if any of hundreds of registry metadata requests fail, then the whole npm install fails. Occasional issue for Angular CLI users.

totally! more developers should try working on Amtrak WiFi — we'd change our 'best practices' very quickly

We'd convince npm to resolve dependencies on the server and return them in a single, resumable HTTP response.

When @sebmck and I were first working on yarn, we did a few waterfall profiles of npm's network call stack. Let's just say that server side resolution of dependency graphs would reduce install times by at least an order of magnitude.