3 ms·
Not OP, but a couple guesses off the top of my head: * It becomes a more painful process to upgrade dependencies (have to find/replace across your codebase).
by freditup 8y ago
Not OP, but a couple guesses off the top of my head:
* It becomes a more painful process to upgrade dependencies (have to find/replace across your codebase).
* Many versions of the same library get pulled in. If you depend on package@1.5.3 and a dependency of yours depends on package@1.5.4, that's twice the dependency size as compared to both just using 1.5.4. This matters more in the case of web app bundle size though than running local programs.
- t-sauer 8y agoYou could have an entry file for your dependencies (let's say dependencies.ts) and reexport everything from there. When you have to update, you only have to upgrade it in the entry file and you can avoid multiple versions.
- wereHamster 8y agoHm, how about we call that file package.json?
- myth_buster 8y agoHow about we link them to modules downloaded onto local file system instead, just in case of network issues.
- WA9ACE 8y agoHow about a cli tool to cache and build those modules/native extensions all at once? We could call that Deno Package Manager.