-
Notifications
You must be signed in to change notification settings - Fork 499
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
Make "fnm" an official installation method for Node.js on Windows #1357
Comments
Here is a related PR on the Node-side of things nodejs/nodejs.org#7365 |
cc @Schniz |
Seems like fnm qualifies as official installer: it downloads binaries as is from Node.js distribution mirror (nodejs.org/dist by default). Zero manipulation happening there. What else should I do to make it happen? |
One last question, so once a new release becomes available on Node side I assume it becomes available immediately on fnm side? I assume fnm probably reads our index.json or something like that? Haven't checked the source. But yeah, that's it. And the fact that we might need to pint you from time to time for questions regarding fnm or issues that people open on our repositories. Pretty much just having a way to contact you through GitHub :) |
(Also if you could check we implemented the snippets correctly, that'd be great!) |
@ovflowd Yes. It uses index.json Relevant source code here: https://github.com/Schniz/fnm/blob/master/src/remote_node_index.rs#L86 |
Then I assume we can proceed and make, fnm an official installation method. Do you feel comfortable with this, @Schniz? |
Landed in nodejs/nodejs.org#7400 |
nice. |
Hi! I'm Claudio from the Node.js team, we recently published a new Downloads page https://nodejs.org/en/download and we'd like to onboard "fnm" as an official installation method. Here are the criteria we are defining of what marks an installation method as official (https://nodejs-org-git-feat-official-community-docs-openjs.vercel.app/en/about/previous-releases#official-versus-community)
How can we proceed with this? ✨
The text was updated successfully, but these errors were encountered: