Gal Schlezinger

> At least it's not a bash alias like nvm 😄 Let's not bash nvm... 😉 but really, nvm's a great product 😄

Yes: * fnm is executed as a binary, compared to a bash function in nvm. So it doesn't need a shell to install or replace node versions * installations are...

When fnm is not being used with the `--multi` flag, it stores a symlink to the current version in `~/.fnm/current`. I'd rather that to stay an implementation detail, this is...

> Also I’d rather not even use `~` anywhere in my scripts. Makes sense 😄 it's not easy on the eyes > 1. Is `fnm exec` on the roadmap? Is...

> Can you expand on this? Why is this a bad idea? I love to avoid mixing my own binaries from the operating system's one. I already started a POC...

Hey @Sparkenstein! Happy to see you here. I'll answer one question at a time 😄 > is it just because it's written in rust? No no, I'm not that kind...

@ljharb Woah! looks great. I'll try benchmarking it too tomorrow!

> A factor of 214 down to 50 is a pretty ridiculously huge speed increase. Kudos for the hard work! Very impressive 😃

Based on your `$PATH`, it looks like `fnm env --use-on-cd | source` was not called. Can you try executing that command manually and see if `node` is available afterwards?

Yes! All the installations and data is stored in the directory $FNM_DIR env var is pointing to. An easy way to set it can be done by adding a `--fnm-dir="..."`...