You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: