-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Deprecation warning with Node 22 #477
Comments
Thanks for raising this. I agree that we can integrate it into concurrently. |
Are you sure, that you want to include the functionality into concurrently? |
@gustavohenke Are you able to realase this soon? |
mmalecki/spawn-command#9 was fixed, so that dependency wasn't actually unmaintained. Instead of including its code in this repo, it would be easier to just bump |
Hi folks, sorry for the delay, this is now fixed in v9.0.0. |
@gustavohenke Thanks for the release. The good news is that the warning is gone. The bad news is that I get a new one now :)
In my case I start over 300 tasks (in the worst case) using concurrently. But the warning appears as soon as I have more than 10 tasks. I also noticed that the |
Ok, let's start a new issue for this one please |
I created #502. |
After upgrading to Node 22 we get a deprecation warning
DEP0060
caused by the dependencyspawn-command
:The code that causes that is this line
The fix looks trivial but
spawn-command
doesn't seem to be developed anymore. Maybe the functionality could be integrated inconcurrently
.The text was updated successfully, but these errors were encountered: