feat: upgrade axios and re-enable gzipping responses #110
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 spent some time today reading through the
axios
docs and issue and I think it should be fine to upgrade to the latest version (0.20.0). It seems to be much more actively maintained than it has been the past year or so, which makes me more comfortable about upgrading. There seem to have been a couple of unintentional breaking changes in this version but neither of them affect us because of how we're using the library in our code.In addition to this version bump, I added the
gzip
encoding on responses back in, which was waiting on a fix withinaxios
.