Gal Schlezinger

There’s a hack I researched. Rehashing on zsh automatically. I’ll open a PR tomorrow and then you can test it before merging. Wdyt?

I do not use VSCode so it'll be hard for me to debug & verify. I don't know what it's running in the integrated shell, etc. `rehash` makes sense, this...

my idea was to call `rehash` before calls to `node` or before any call (yet this feels... not good 😁)

I was thinking about adding an optional `node` and `npm` wrappers that forward everything to `fnm exec` for these kind of situations, that can be installed with: ``` $ fnm...

what can we do to make this work nicer for y'all? allow to make the initial/all `fnm use` on `cd` quiet? `--use-on-cd=quiet` and `--use-on-cd=quiet-init`?

this is a permissions thing. I don't assume anything about your setup but I guess the following should work: ```bash sudo "$(which fnm)" exec --using="$(fnm current)" npm --version ``` let's...

Hi, thanks for this. Really helpful. I wonder whether this would be easier if you have tried the installation script/Homebrew installation process. I also consider suggesting to use the installation...

Is there a logical reason why to use a Windows executable on WSL? Are there issues installing the Linux one?

I would be surprised if fnm.exe will work because IIRC when we stringify the paths it's using the path separator given statically by the compiler (so on \*nix is `/`...

Hi! sorry for the delay. I don't know corepack so much, so I'm sorry if my questions are stupid: > Unfortunately, switching to a new Node.js version with fnm requires...