Skip to content
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

consider supporting .node-version spec #2292

Closed
ScottChapman opened this issue Aug 26, 2020 · 3 comments
Closed

consider supporting .node-version spec #2292

ScottChapman opened this issue Aug 26, 2020 · 3 comments
Labels
feature requests I want a new feature in nvm!

Comments

@ScottChapman
Copy link

Please see https://github.com/shadowspawn/node-version-usage

This would allow projects to be more node version manager agnostic

@ScottChapman ScottChapman changed the title consider supporting .node-version spec consider supporting .node-version spec Aug 26, 2020
@ljharb
Copy link
Member

ljharb commented Aug 26, 2020

The reasons why it's prohibitive for nvm to support this are discussed here.

@ljharb ljharb added the feature requests I want a new feature in nvm! label Aug 26, 2020
@shadowspawn
Copy link

shadowspawn commented Sep 7, 2020

See also: #794 and #1625

Supporting a simple static version does not seem prohibitive?
#794 (comment)

(To be clear relative to the title of this issue, there is not a spec for .node-version. There are some existing implementations. 🙂 )

@ljharb
Copy link
Member

ljharb commented Sep 7, 2020

Ah yes, thank you. Duplicate of #794, in particular.

(Supporting a single static version is fine if that's all other tools support too. A common filename with tools inconsistently supporting formats in it is a recipe for disaster)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature requests I want a new feature in nvm!
Projects
None yet
Development

No branches or pull requests

3 participants