You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since contributors can't modify yarn.lock, this is an issue to track what was #204251
Basically, npm-run-all is no longer actively maintained and there's now a better maintained npm-run-all2 which is actually lighter, has security fixes, etc.
Would make sense to move across (many already have).
Low priority but should be an easy enough drop-in replacement (it is a direct fork)
The text was updated successfully, but these errors were encountered:
I started the fork because I use run-{p,s} everywhere and wanted to see its ongoing maintenance continued. We're at 40k public repos adopting the fork so far, and are a designated replacement package in renovate bot. The plan for the fork is to keep maintaining the project pretty much as is for the foreseeable future.
Big user of VSCode of course and would love to help out in a small way with this. If you run into any issues let me know but it should be a drop in replacement (same bin names).
Since contributors can't modify
yarn.lock
, this is an issue to track what was #204251Basically, npm-run-all is no longer actively maintained and there's now a better maintained
npm-run-all2
which is actually lighter, has security fixes, etc.Would make sense to move across (many already have).
Low priority but should be an easy enough drop-in replacement (it is a direct fork)
The text was updated successfully, but these errors were encountered: