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

[voxpelli]

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.

• Use maintained fork of npm-run-all typicode/json-server#1446
• Use maintained fork of npm-run-all emberjs/ember.js#20523
• Swap to maintained fork of npm-run-all nhoizey/pack11ty#544 (No PR yet)
• chore: use maintained npm-run-all fork eslint-community/eslint-plugin-n#124

[bcomnes]

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]

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]

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

[travi]

i finally got a chance to open renovatebot/renovate#25085

[bcomnes]

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.

[viceice]

replacement merged and live since v37.7.0 of renovate

[voxpelli]

@viceice Yay!

[bcomnes]

About to cross 13k dependents. Thank you @travi and anyone else involved. I hope we can serve the ecosystem well! Closing as DONE!