Holy hell. Look how many people are commenting about their production environment being affected by this issue. All these folks had not even the simplest test/checks in place before pushing changes to production. And they're openly admitting to it by complaining about an issue with a dependency they just YOLO'd and shipped.
> Can repro. This is causing major issues with an electron app of mine. Axios is used via unpkg versionless inside of the asar and there is no way to notify users to update as all requests to autoupdater are handled through axios... This should be reverted, and such a breaking change should have been communicated well in advance (and NOT distributed under a semver minor change!!)
why are there so many downvotes for comments that are sharing/confirming their own issues with the library? Seems pretty terrible/unconstructive if those are all from the maintainers of the library
In retrospect these people posting in the issurs should probably be pinning their dependencies, but at the same time it does kind of reflect poorly on the engineering leadership at Axios that they would inadvertently ship something that isn't backwards compatible in a minor version bump (looks like changes in the 1.1.0 release, updated from 1.0.0 is what is causing the issue)
If you're installing a specific version of your code on user machines but fetching the latest version of your dependencies from the internet every time your app starts I'm going to find the resulting pain kinda amusing.
