Update npm-run-all to the latest version 🚀 #860
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
greenkeeper
bot
added
the
Type: Dependencies
astorije
approved these changes
Jan 2, 2017
There was a problem hiding this comment.
Checked this out locally, played a bit with npm install, npm test, npm run watch and everything seems fine.
It looks like we are not affected by the breaking changes. Breaking: drop supports for Node 0.x works for us because we dropped it earlier anyway. I'm not too sure what the breaking change for Breaking: use NPM_EXECPATH to run tasks is though, but local tests seemed OK.
xPaw
approved these changes
Jan 3, 2017
matburnham
pushed a commit
to matburnham/lounge
that referenced
this pull request
Sep 6, 2017
…ll-4.0.0 Update npm-run-all to the latest version 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 4.0.0 of npm-run-all just got published.
The version 4.0.0 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-run-all.
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 15 commits .
5e88fb74.0.012b2b87Breaking: use NPM_EXECPATH to run tasks07bfec5Chore: remove unused setting in .eslintrc.json02e9767New: --max-parallel option58f9d4cChore: remove read-pkg-up49528e4Chore: update dependencies023a3c3Fix: the leaks of modifications to remove babel26a951eChore: upgrade nyc and mochac8c440dChore: stop using babel993df33Chore: remove polyfills3f933c3Chore: upgrade eslint and eslint-config53d4f2aBreaking: drop supports for Node 0.xfed85bfChore: rename .eslintrc → .eslintrc.json910d78dMerge pull request #75 from nulltask/feature/colorize (fixes #73)d7821dfChange labels to be displayed in individual colors for each taskSee 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 🌴