I started using NVM, the Node version manager. Then installed Haxe and Lix. Lix installed haxeshim, and caused NVM to alias haxe to haxeshim.
The default haxeshim points to haxe 4.2.5, and even when I configure a Lix project to use “haxe latest” which is 4.3.7, Lime still wants to use the default one that haxeshim uses. This is true even when I use “lix lime” to run Lime. Any tips on how to get Lime obeying the haxeshim setting would be appreciated. Or how to change the default for haxeshim alternatively.
1 Like
This only became an issue because neko was not being allowed to run properly. It was complaining about the arm64 architecture of my Apple silicon machine. Now I run Lime via Rosetta using the command arch -x86_64 zsh before building, which activates it for the current terminal. This resolves the complaints about the arm64 architecture.
I reinstalled Lime to fix this, and ran haxelib run lime setup.
I believe this started after I upgraded to MacOS Tahoe and installed some of my Haxe/OpenFL stack.
It was NVM which broke the Lime setup.
I installed Node version 24 (~/.nvm/versions/node/v24.13.0/bin/) and 20 (~/.nvm/versions/node/v20.20.0/bin/node). Problem is, Lime thinks Node lives at usr/local/bin which is the usual.
So the final step is create a symlink there to the NVM version of my choice.
