is there a way to ignore .nvmrc

[a-b-r-o-w-n]

I have a project with a .node-version and .nvmrc with different node versions set. fnm use complains that I don't have the version found in .nvmrc installed and asks me to install.

Is there a way to disable checking of .nvmrc?

[thasmo]

Does nvm prioritize the .node-version file over the .nvmrc file? If so, it would be nice to have the same behavior in fnm, I guess.

[a-b-r-o-w-n]

I'm not sure what nvm does, and my request isn't that this is done automatically. Most projects will only have a single node version file, but in our case devs with M1 macs are using node 16 instead of node 14. I was thinking an environment variable that could set a node version file lookup path:

FNM_VERSION_FILE_PATH=".node-version:$FNM_VERSION_FILE_PATH

[ljharb]

@thasmo nvm intentionally does not support the nonstandard .node-version file at all.

[Schniz]

I have a project with a .node-version and .nvmrc with different node versions set

[Schniz]

Most projects will only have a single node version file, but in our case devs with M1 macs are using node 16 instead of node 14.

on a more serious note, this feature is possible to implement and should be fairly easy to do but I think it is wrong. If your production env is Node 14, then M1 macs should use Node 14. If you want to use 16, use 16. Don’t mix them up. If you already know that the app works well on Node 16 why not upgrade it to everybody?

if the solution is allowing M1s to use Node 14 then it’s possible to implement however with the latest changes of MacOS seems like it will require to install Python 2 to do that which is a big barrier. Since EOL is next year I’m not sure that the effort is worth it

[ljharb]

I 100% agree. M1 Macs can use node 14 via Rosetta just fine though.