kit's version of node (15) is overriding my own version from n

[kentcdodds]

No matter what I do, my node resolves to one installed by kit which is causing me a bunch of issues because kit's version is 15...

~/code/remix-kentcdodds (main) 🧞‍
$ node --version
v15.13.0
~/code/remix-kentcdodds (main) 🧞‍
$ n
   installed : v16.9.1 to /Users/kentcdodds/n/bin/node
      active : v15.13.0 at /Users/kentcdodds/.kit/node/bin/node
~/code/remix-kentcdodds (main) 🧞‍
$ which node
/Users/kentcdodds/.kit/node/bin/node
~/code/remix-kentcdodds (main) 🧞‍
$ 

I use https://npm.im/n to manage my node version and even after selecting v16.9.1, it's still using node 15 from kit. I've closed and opened the terminal and everything. I can't get it to use the version from n. :(

[johnlindquist]

🤔

This might be an issue from an older Kit install.

Can you paste the result of echo $PATH | pbcopy?

Kit shouldn't have affected your $PATH (which controls the order the terminal searches for commands), but maybe some old config did something we need clean up.

[johnlindquist]

Aha! Hmm, good catch. I'll get that sorted.

A "quick fix" might be:

export PATH="Users/kentcdodds/n/bin:$PATH" in your vs code terminal. Then n/bin should take priority in any future process.

[johnlindquist]

Also, just to confirm, "Launch code from Kit" means you're using the edit() function in a Kit script?

[kentcdodds]

The grep finally finished and the only interesting thing that came out of it was this:

/Users/kentcdodds/Library/Containers/com.docker.docker/Data/log/host/com.docker.supervisor.log.2
2078:time="2021-08-12T09:29:43-06:00" level=info msg="pidfile \"com.docker.vpnkit\" references Pid 630 but paths differ: assuming pid re-use, removing it\n   expected: \"/Applications/Docker.app/Contents/Resources/bin/com.docker.vpnkit\"\n  effective: \"/Users/kentcdodds/.kit/node/bin/node\"\n"

Not sure whether that's related, and I'm not even sure what it's doing but I thought it was interesting.

[kentcdodds]

Also, just to confirm, "Launch code from Kit" means you're using the edit() function in a Kit script?

Yes

[johnlindquist]

edit does unnecessarily load .kit/node/bin onto the PATH*, so it seems like that's the culprit

I see it happening in my VS Code env, but in my PATH my node is installed at /usr/local/bin which precedes /Users/johnlindquist/.kit/node/bin so I didn't notice.

*It's sharing PATH with the await npm() util which requires .kit/node/bin on the PATH, so I'll have to separate them.