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

move to npm-run-all2 in dev scripts #204398

Open
43081j opened this issue Feb 5, 2024 · 1 comment
Open

move to npm-run-all2 in dev scripts #204398

43081j opened this issue Feb 5, 2024 · 1 comment
Assignees
Labels
debt Code quality issues tasks Task system issues

Comments

@43081j
Copy link

43081j commented Feb 5, 2024

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)

@bcomnes
Copy link

bcomnes commented Aug 9, 2024

Hi! Maintainer of the fork here.

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debt Code quality issues tasks Task system issues
Projects
None yet
Development

No branches or pull requests

3 participants