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-plugin-istanbul.
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.
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.
Coverage remained the same at 100.0% when pulling f9a99b1a3a1b593df18a7c069a936950098291e7 on greenkeeper-babel-plugin-istanbul-4.0.0 into cc0892efd71bdeed443509b08423d7ff493d9c43 on master.
Hello lovely humans,
babel-plugin-istanbul just published its new version 4.0.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-plugin-istanbul. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 27 commits .
ac8abab
chore(release): 4.0.0
e902924
fix: load configuration from process.env.NYC_CONFIG if present (#93)
f77db2a
feat: we can now use the language feature Object.assign (#92)
80afed9
docs(readme): add Greenkeeper badge 🌴 (#89)
594c03a
feat: drop Node 0.10 and 0.12 support, upgrade dependencies to reflect this (#88)
f0b8d7e
chore(package): update test-exclude to version 4.0.0 (#86)
86c1c09
chore(release): 3.1.2
f870a8f
fix: address regression related to export const foo = () => {} (#79)
73a4247
chore: explicitly upgrade istanbul-lib-instrument
9818c25
chore(release): 3.1.1
18bbcdc
chore: upgrade to version of istanbul-lib-instrument that addresses inferred function name issues
2e0af61
chore(release): 3.1.0
e764330
fix: upgrade a bunch of core dependencies (#77)
437e90b
feat: accept source map input for the visitor (#75)
7bd4eb8
chore(package): update standard-version to version 4.0.0 (#73)
There are 27 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.