Skip to content
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 🚀 #11

Merged
merged 1 commit into from
Jun 3, 2017
Merged

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Jun 3, 2017

Version 11.0.2 of nyc just got published.

Dependency nyc
Current Version 10.3.2
Type devDependency

The version 11.0.2 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 13 commits.

  • 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
  • 55b68b5 chore: update istanbuljs dependencies (#583)
  • a1a457f feat: allow .nycrc.json (#580)

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 🌴

@coveralls
Copy link

coveralls commented Jun 3, 2017

Coverage Status

Coverage remained the same at 99.153% when pulling e86668d on greenkeeper/nyc-11.0.2 into 9193d28 on master.

@diegohaz diegohaz merged commit b357d01 into master Jun 3, 2017
@diegohaz diegohaz deleted the greenkeeper/nyc-11.0.2 branch June 3, 2017 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants