No, Go solves this problem and Deno explicitly copies its design. Just use Go. Seriously. The stupidest thing npm still does today is naively assume SemVer is an appropriate strategy for automatic updates.
There is so such thing as an appropriate strategy for automatic updates for developers. For end users? Sure. Because the assumption for them is that things are stable.
Developers need to check. Developers need to pin.
If you’re working in the Node.js ecosystem the solution isn’t to throw the baby out with the bath water and use Deno, it’s to `—save-exact`.
I’m sure as hell not throwing away all of the hours invested in now stable JavaScript software.
There is so such thing as an appropriate strategy for automatic updates for developers. For end users? Sure. Because the assumption for them is that things are stable.
Developers need to check. Developers need to pin.
If you’re working in the Node.js ecosystem the solution isn’t to throw the baby out with the bath water and use Deno, it’s to `—save-exact`.
I’m sure as hell not throwing away all of the hours invested in now stable JavaScript software.