Update axios to v0.21.0 #250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will prevent BOM characters from throwing off JSON parsing. More info: - https://github.com/axios/axios/releases/tag/v0.21.0 - https://github.com/axios/axios/releases/tag/v0.20.0-0
jamonholmgren
approved these changes
Oct 26, 2020
infinitered-circleci
pushed a commit
that referenced
this pull request
Oct 26, 2020
# [2.0.0](v1.1.2...v2.0.0) (2020-10-26) ### Features * **deps:** Update axios to v0.21.0 ([#250](#250) by [@developius](https://github.com/developius)) ([32ff13b](32ff13b)) ### BREAKING CHANGES * **deps:** Update axios to v0.21.0
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I discovered an issue when using apisauce with one of our endpoints.
Our server runs on ASP.NET and returns a byte order mark in responses. Axios wasn't correctly handling this prior to v0.20.0-0 which meant JSON.parse would blow up.
Axios released v0.20.0-0 and v0.20.0 which fixed this particular issue, but introduced a TypeScript compilation error which has been fixed in v0.21.0.
More info: