Update babel-preset-env to version 1.3.0 🚀 #3
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.
Hello lovely humans,
babel-preset-env just published its new version 1.3.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of babel-preset-env.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
v1.3.0 (2017-03-30)
🐛 Bug Fix
We now properly check for
Symbol.species
support in ArrayBuffer and include thepolyfill if necessary. This should, as a side effect, fix ArrayBuffer-related
errors on IE9.
💅 Polish
We've simplified things by adding
electron
as a target instead of doing a bunch ofthings at runtime. Electron targets should now also be displayed in the debug output.
If you are targeting the
node
environment exclusively, the always-included web polyfills(like
dom.iterable
, and a few others) will now no longer be included.📝 Documentation
🏠 Internal
The new version differs by 8 commits .
8b2dc4f
1.3.0
6ebf857
Update changelog
046f326
Add check for ArrayBuffer[Symbol.species] (#233)
aead61c
Fill data with electron as a target. (#229)
48a329b
separate default builtins for platforms (#226)
a4d585c
remove deprecated projects (#223) [skip ci]
88cbe17
Merge pull request #216 from babel/update-npmignore
cf94af3
npmignore: Add related to build data and codecov.
See the full diff.
Screencast
Try it today. Free for private repositories during beta.