Update npm-run-all to version 4.0.1 🚀 #124
Closed
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
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.
Hello lovely humans,
npm-run-all just published its new version 4.0.1.
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-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.
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 ✨
You rock!
🌴
GitHub Release
Bug fixes
npm_execpathon Mac/Linux (#84).Thank you, @bmarcaur !
The new version differs by 75 commits .
acb15824.0.1378c54bChore: switch to codecov779720cChore: fix trivial6beda60Docs: update README.md558da4bMerge pull request #82 from vinkla/patch-1181b689Merge pull request #84 from bmarcaur/fix/npm-execpath-case-sensitivitybb9e627NPM_EXECPATH -> npm_execpath, this variable is case sensitive81e3d0fMerge pull request #83 from evilebottnawi/patch-2b40fc7eFixed: typo inhelpCLI command.0190327Simplify repository config750f5d9Docs: fix README.md5e88fb74.0.012b2b87Breaking: use NPM_EXECPATH to run tasks07bfec5Chore: remove unused setting in .eslintrc.json02e9767New: --max-parallel optionThere are 75 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade