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 npm-check-updates.
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.
Hello lovely humans,
npm-check-updates just published its new version 2.10.4.
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 npm-check-updates. 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:
GitHub Release
Fixes #329 with PR #332.
The new version differs by 18 commits .
14dfe69
2.10.4
9dcead2
yarn
3ee2c50
Cleanup and fixes for pull request
92d26c6
Turning on eslint for test dir
2aa4c9b
Using tmp package for cwd of spawned ncu
2554160
replacing child_process use with spawn-please
c08b959
removing .only from test
adb2495
Fixing error when there's no stdin or package.json in fs hierarchy
5efc915
Add snyk. Update dependencies.
7796c11
Rename corresponding functions in tests.
013fbd4
Rename pkg to pkgData for consistency.
df84445
Rename getLatestVersions to queryVersions.
960d3f7
Rename updatePackageData to upgradePackageData.
19e4317
Move upgradePackageDefinitions to vm.
5285b73
Extract getPackageData from programRunLocal.
There are 18 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.