Gal Schlezinger
Gal Schlezinger
d1f7b9d is because I thought I would be able to change the symlink generation process from random to using the parent process' pid, and therefore making it reproducible, and making...
> Shells are obviously not the common denominator (the shims are a shell script) CLI (pid1) -> node shim (pid2) -> fnm (pid3) fnm tries to take pid2, instead of...
The premise of reproducible "multishell" paths is good, because it simplifies the installation of fnm, which can be awesome.
We can have `fnm exec --fallback-to-default` but I am not sure this is enough.. what if someone wants to change a node version? I just wonder if there's a better...
Hmm I don't know anything regarding apt, but it could be nice. Do you know how to create a repository? Can it use GitHub packages? Maybe that'll be the easiest...
It is not currently supported. Sorry! But it is interesting.
> I set the appropriate mirror env variable to the unofficial one would you mind sharing the unofficial mirror? 😄
(taken from #274 comment:) Potentially refactor for #239, most of this will be used in `cfg!` if statements instead of `#[cfg]` and maybe we'll have a PLATFORM constant that we...
What do you mean "from an application"? A CI step? Try ``` eval "$(fnm env)" ``` Another option is to `fnm exec -- npx ...`