-
Notifications
You must be signed in to change notification settings - Fork 426
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
--use-on-cd should revert to default node #442
Comments
The way I would want it is. If you navigate into a child folder (without a However when navigating to the parent folder of the folder with a |
This is how nodenv behaves
|
Adding the ability to provide `--version-file-strategy=recursive` on both `fnm env` and on each command can allow us to support recursive resolutions of the Node versions. This makes the default Node version as easy as: ```bash echo "16" > ~/.node-version ``` (assuming your code lives inside your home directory) and fixes #442, if becomes the default. --- This fixes #144 which is a very old issue 😃 #144 (comment)
Sorry that I had no response. #607 is what I had in mind for this. Now that I think about it, I can add the default version if it finds nothing. |
Was this feature ever implemented? Even though this issue is closed, the node version is not being changed if I Test in PowerShell: Test in bash (just to make sure it is not due to #513): WorkaroundCreate an |
Yes, but it requires an extra argument: eval "$(fnm env --use-on-cd --version-file-strategy=recursive)" |
The flag
--use-on-cd
should revert to default node if there is no.nvmrc
present.Is this already the case? Because it's just staying on the last used node version when switching in directories without one.
The text was updated successfully, but these errors were encountered: