Repository navigation
Conversation
pederbe
marked this pull request as ready for review
November 12, 2026 16:23
Owner
|
so |
Author
@Schniz Yes, It resolves the version on each command rather than using fnm’s stored |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An
.nvmrccontainingnodecurrently fails because fnm treats it only as a custom alias. Support this nvm-compatible spelling in version files and command arguments, selecting the latest installed stable version locally or the latest stable release for installation. Existing aliases namednodekeep their behavior.The shell regression fails on the original implementation and passes with this change, using a fixed release index and real Node.js executables in Bash, Zsh and Fish.
Fixes #1506.