-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update nyc to the latest version 🚀 #53
base: master
Are you sure you want to change the base?
Conversation
Version 11.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 5 commits.
See the full diff |
Version 11.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 11.2.1 just got published. |
Version 11.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 11.4.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Version 11.6.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 11.7.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 11.7.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 11.7.3 just got published. |
Version 11.8.0 just got published. |
Version 12.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 12.0.2 just got published. |
Update to this version instead 🚀 CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
|
Update to this version instead 🚀 CommitsThe new version differs by 48 commits.
There are 48 commits in total. See the full diff |
|
|
Version 11.0.3 of nyc just got published.
The version 11.0.3 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 nyc.
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.
Commits
The new version differs by 17 commits.
e9fad9f
docs: add note about tap-nyc to README (#614)
f86b0b1
chore(release): 11.0.3
923b062
fix: upgrade to spawn-wrap version that works with babel-register (#617)
b1eb4d6
fix: update help link to list of reporters (#601)
e4eff12
chore(release): 11.0.2
0c2ef43
chore: upgrade to newer version of spawn-wrap (#592)
9d47986
chore(release): 11.0.1
fa1097a
chore: acutally swap in new copy of signals.js
8662357
chore: hack to fix SIGPROF binding issue on node 8
d90aed6
chore(release): 11.0.0
2f68559
chore: hack to prevent SIGPROF warning, until new spawn-wrap is available
f18f780
fix: add support for ES6 modules
0e6b277
chore: formatting nit
80ef0a3
docs: mention the ability to publish configuration in docs
33829b8
feat: upgrade to version of yargs with support for presets
There are 17 commits in total.
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 🌴