Notify large users of `npm-run-all` that they may want to switch

bcomnes / npm-run-all2

A CLI tool to run multiple npm-scripts in parallel or sequential. (Maintenance fork)

MIT License

262 stars 13 forks source link

Notify large users of `npm-run-all` that they may want to switch #118

Closed voxpelli closed 10 months ago

voxpelli commented 1 year ago

Equivalent to https://github.com/eslint-community/eslint-plugin-n/issues/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 https://github.com/eslint-community/eslint-plugin-n/issues/100.

bcomnes commented 1 year ago

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.

travi commented 1 year ago

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.

bcomnes commented 1 year ago

That's a great idea. I wonder what they would do in this situation. Worth a shot even if it's not accepted.

travi commented 1 year ago

i finally got a chance to open https://github.com/renovatebot/renovate/pull/25085

bcomnes commented 1 year ago

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.