You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version is covered by your current version range and after updating it in your project the build failed.
As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
We now properly check for Symbol.species support in ArrayBuffer and include the
polyfill if necessary. This should, as a side effect, fix ArrayBuffer-related
errors on IE9.
💅 Polish
Fill data with electron as a target. (#229) (@yavorsky)
We've simplified things by adding electron as a target instead of doing a bunch of
things at runtime. Electron targets should now also be displayed in the debug output.
separate default builtins for platforms (#226) (@restrry)
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.
Version 1.3.0 of babel-preset-env just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v1.3.0v1.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
Commits
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.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: