3 ms·
- bundles let you ship less code (tree shaking) - dependency versions being fixed is a feature. I've had package installs fail because a dependency published a
by andreareina 4y ago
- bundles let you ship less code (tree shaking)
- dependency versions being fixed is a feature. I've had package installs fail because a dependency published a semver-compatible update that broke something. In a web context this would break the app until the dependency pulled the update or the dependent pushed an update disallowing that version.
- _ZeD_ 4y ago> - bundles let you ship less code (tree shaking) bundling should be done as a step to build an application. it's really not needed when you prepare a library. > - dependency versions being fixed is a feature. I've had package installs fail because a dependency published a semver-compatible update that broke something. If this is the case please open a bug to the dependency team. And then avoid ^ ~ and * in the dependencies version you are using.
- andreareina 4y agoI missed that the article was talking about server/library code, I had client/application code on the brain.
- laundermaf 4y ago> dependency versions being fixed is a feature Pushing multiple versions of the same library is a bug. Semver ranges exist for a reason. > a dependency published a semver-compatible update that broke something The same can happen with your direct dependencies too. Just use a lockfile and only update it when the install is successful. > In a web context this would break the app Absolutely not. Use lockfiles. Nothing breaks until you merge that update PR.
- andreareina 4y agoYeah I missed that the article was only talking about libraries, I was thinking about client code. Agreed it's not an issue for library/server code.