Repository navigation
Take over node-versions package #605
Description
This package gets 40M downloads a week and has not been seeing regular publishes. I asked the maintainer if they would be interested in maybe handing it off and it looks like they are. Anyone opposed to pulling this functionality into @pkgjs/nv or working with the @nodejs/build or @nodejs/releasers to see if publishing this right from the release workflows makes sense?
I think it would be really simple to pull it in as a nightly in nv which was discussed briefly in pkgjs/nv#10. If folks are open to this I can start the work to do that. If not I do think that publishing updated metadata to the npm registry at release time is a great longer term solution to folks needing this data.
cc @chicoxyzzy
Activity
ljharb commentedon Jul 16, 2024
It's a great approach - I do the same thing in my github actions, cached here (instead of published to npm)
chicoxyzzy commentedon Jul 16, 2024
I'm open to transfer https://github.com/chicoxyzzy/node-releases to the Node.js GitHub organization if that could help in a short term.
wesleytodd commentedon Jul 16, 2024
I am not sure that would help right now. Until we can pick a longer term direction I think it would be best to hold the course. Thanks for updating the package, that helps make any delayed decision easier, but I don't have time to take it over myself right now and I don't want to transfer things in unless they are well accounted for to be taken care of.