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

resolve-engines / FNM_RESOLVE_ENGINES always chooses latest instead of current #1339

Open
jakebailey opened this issue Dec 1, 2024 · 0 comments

Comments

@jakebailey
Copy link

Hi there; I went to figure ouy why my node install kept changing from my default when moving into certain repos and discovered the FNM_RESOLVE_ENGINES option. The help message said to file an issue with feedback since it seems like the option may go away.

I've disabled the option for a couple of reasons:

  • The option seems to switch versions even if the version I already have is good enough.
  • My default is 22, but I also have 23 installed. 22 is the latest stable version, while 23 is "latest" but as an odd version, typically not used. But, fnm appears to switch to the newest version of whatever I have installed, whcih is some random version of 23 I had been testing.

It seems to me that not changing versions if the currently active one is "good enough" would be sufficient to avoid both of these issues. I regularly update my default to the latest even version, which should be good enough for anything I am working on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant