Honor .node-version file
Forgive me if this has been discussed before, but I didn't find anything beyond https://github.com/creationix/nvm/issues/110#issuecomment-40525629. It would be really nice to see the various Node version managing tools coalesce around a common "version config file", analogous to Ruby's `.ruby-version` for RVM and rbenv - `.node-version`. This would basically just be an alias for `.nvmrc`, since that functionality's already been added. Since `n` already supports `.node-version`, this would make it so that regardless of the Node version manager used, there could be some degree of guarantee that the correct version will be used.
Posted by mnquintana on Aug 4, 2015, 1:12 AM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
Honor .node-version file
Forgive me if this has been discussed before, but I didn't find anything beyond https://github.com/creationix/nvm/issues/110#issuecomment-40525629. It would be really nice to see the various Node version managing tools coalesce around a common "version config file", analogous to Ruby's `.ruby-version` for RVM and rbenv - `.node-version`. This would basically just be an alias for `.nvmrc`, since that functionality's already been added. Since `n` already supports `.node-version`, this would make it so that regardless of the Node version manager used, there could be some degree of guarantee that the correct version will be used.
Comments (0)
No comments yet. Start the discussion.