-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Notify large users of npm-run-all
that they may want to switch
#118
Comments
Thanks for doing that! I haven't looked into the dependency graph of upstream yet but if we ID some bigger projects, perhaps they are interested. |
have you considered defining a replacement within renovate? i added this definition to my personal config, and updates of my projects have been smooth. i thought i'd check in here before contributing a similar PR to renovate itself. in case you are not familiar with the contribution process for defining replacement definitions, here are some examples of others i've contributed. in the ones that i've contributed, the original packages were deprecated, so it was easy to make it clear that the project recommended migrating to the replacement. that would be different in this case, so that might be worth a conversation with the renovate team. |
That's a great idea. I wonder what they would do in this situation. Worth a shot even if it's not accepted. |
i finally got a chance to open renovatebot/renovate#25085 |
Thank you for doing that @travi! I hope they accept the replacement suggestion. It would be great to get even more people benefiting from the maintenance we are doing here. |
replacement merged and live since v37.7.0 of renovate |
@viceice Yay! |
About to cross 13k dependents. Thank you @travi and anyone else involved. I hope we can serve the ecosystem well! Closing as DONE! |
This is closed, but I'm going to start adding a trail of PRs I open. Feel free to unsubscribe if it gets too noisy. |
Whoa missed that one. Thanks for the heads up @Jayllyz. |
Equivalent to eslint-community/eslint-plugin-n#100. It can be hard for users of
npm-run-all
to find out that there's a maintained fork of the project, so notifying some of them to help them out. Mostly in tandem with the work in eslint-community/eslint-plugin-n#100.npm-run-all
typicode/json-server#1446npm-run-all
emberjs/ember.js#20523npm-run-all
nhoizey/pack11ty#544 (No PR yet)npm-run-all
fork eslint-community/eslint-plugin-n#124The text was updated successfully, but these errors were encountered: