Update babel-preset-env to version 1.4.0 🚀 #78
Closed
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.4.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.4.0 (2017-04-14)
🚀 New Feature
specoption (#98) (@Kovensky)Added an option to enable more spec compliant, but potentially slower, transformations for any plugins in this preset that support them.
We updated our mappings so that you can get native support for async/await and other goodies when targeting Edge 15!
🐛 Bug Fix
Fixed a bug that was ignoring Android targets in browserslist queries (for example: "Android >= 4").
📝 Documentation
🏠 Internal
The new version differs by 23 commits .
125e9281.4.0e22c26cUpdate changelog [skip ci]2aaecc5Supportspecoption (#98)8bca925Clarify note about loading polyfills only once (#282)2135fb9Add a reminder about include/exclude options (#275)40da88eChore: reduce package size. (#281) [skip ci]cad1b2bMerge pull request #273 from babel/compat-table7033974Bump compat-table for Edge 15 support38a1369Remove deprecated comment (#271)d197aa0Merge pull request #270 from babel/issue268c0d641eAdd Android browser to name mapa2224531.3.3801c6d4Fix and update changelog for v1.3.3 [skip ci]8701755Ensure const-check plugin order (#257)19bd172Update changelog (#253)There are 23 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.