This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
babel-preset-env just published its new version 1.3.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 :sparkles:
You rock!
:palm_tree:
GitHub Release
v1.3.0 (2017-03-30)
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.
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.The new version differs by 88 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.
40c3a1f
v1.2.2 changelog [skip ci]
e186f2d
1.2.2
ac9cf86
Change how yarn is installed on travis
81a7a82
Merge pull request #198 from yavorsky/typed-ie
491dc2c
Add typed array methods to built-ins features.
ed59056
Merge pull request #208 from babel/issue207
0cd96f5
address review comments
There are 88 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.