4 ms·
All these comments on GitHub are amazing to me. How do you let a new build of your project with a new version of a such a fundamental dependency get deployed t
by mb7733 4y ago
All these comments on GitHub are amazing to me. How do you let a new build of your project with a new version of a such a fundamental dependency get deployed to _production_ without being tested first, manually or otherwise?
- junon 4y agoYeah, you should definitely ask for a refund!
- simon04 4y agoHere's the refund form: https://notepad-plus-plus.org/news/v843-unhappy-users-edition/ https://notepad-plus-plus.org/news/v843-unhappy-users-editio...
- mb7733 4y agoYou misunderstand me. I'm not criticizing the axios developers, I'm criticizing downstream developers that blindly deploy new versions to production. Many of these products are likely commercial based on their comments
- joshstrange 4y agoMy guess is they didn't deploy a new version but rather they used a CDN... for a mobile app... I can't even. Not pinning and not testing is egregious enough but to use a CDN for a web-based cross-platform app? Absurd.
- Matthias247 4y agoMore specifically: A public CDN whose content they don't own, and that can change at any point in time. If it would be a private CDN which points only to the content they explicitly published as part of a build&release process they wouldn't have the problem. If you rely on public artifacts that others published, all your availability and security guarantees are gone.