Replace babel-preset-latest with babel-preset-env #2
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.
While lamenting the spotty support for ES6 in modern tooling, I stumbled upon your article on making a wrapper for fetch in ES6. Thank you for sharing your experiences.
I thought you might be interested in the fact that
babel-preset-latest
appears to be deprecated in favor ofbabel-preset-env
. The babel docs say that the "env" preset with no options acts just like the "latest" preset.Feel free to do whatever you want with this PR. I just wanted to try and give you a little help keeping one of your projects up-to-date 😉👍