-
Notifications
You must be signed in to change notification settings - Fork 460
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
Add support for .node-version files #8
Comments
I’d suggest not using it; it’s not actually a standard, and in fact it’s current use means that the Node Version Management Group will (when it only day creates a standard) be defining a different file name and format. |
We already use Would be cool if these projects could work with fnm too. Would it be a huge change to add support for it? I would like to understand the disadvantage of adding support for it |
The disadvantage is yet another version manager implying that this file is a standard, when in fact it isn’t and can never be. |
Well people don’t need to use it - it just adds compatibility to sth what’s already commonly used It also supports |
Right - I’m saying that it’s better to be less compatible, so as to help make that format less commonly used, because it will one day be very harmful for the ecosystem to have that file as the commonly used one. |
So if I understand you correctly we should also drop support for |
If you like, but Whatever filename we go with will be something new that is not tied to any specific version manager. |
4 of 6 node version managers (which work for mac, windows and linux) support would love to know what @Schniz thinks about this |
The instant the node version management working group declares a standard format, it won't be ¯\_(ツ)_/¯ (and we won't be declaring ".node-version") |
I’m not familiar with |
Cool :) There are already 45.000 Github repositories using a The content is very simple but in the early days there were two formats:
Nowadays all version managers seem to skip the nvs just says that the nodist uses a similar description like nvs avn also notes that the |
This is exactly how I implemented the This can be by changing the If someone needs any help with implementing it, reach me out with a DM or an Email or something. I'd love to help! The only thing worth noting is that we'll need to have some kind of priority. |
@Schniz Just dropping in to say thanks and great work! A new tab in Hyper went from ..... to . as soon as I installed fnm and switched off nvm. My two cents on the above discussion is that it appears the WG hasn't met in two years and the initial proposal, IMHO, doesn't make a compelling argument for creating what amounts to yet-another-version-manager with an official stamp. Adding support for a de facto standard cross-vm config like I would love to show my gratitude with a PR but I am short on time at the moment, I will check back this weekend to see if this or another GFI is open. |
adding support for `.node-version` files, along with `.nvmrc` files Resolves #8
Most version managers support the
.node-version
format:Could you please also add support?
The text was updated successfully, but these errors were encountered: