fnm icon indicating copy to clipboard operation
fnm copied to clipboard

šŸš€ Fast and simple Node.js version manager, built in Rust

Results 301 fnm issues
Sort by recently updated
recently updated
newest added

as title describes, this is a configuration change for Changesets.

automerge

Iā€™m guessing this is because of the manual release process, as mentioned in #517. It would be great to get v1.31.0.

I was able to make older Node.js builds available for ARM (Apple Silicon / M1) on an internal mirror (provided to fnm with `--node-dist-mirror`) but it is impossible to get...

![image](https://user-images.githubusercontent.com/43396684/177704605-39241be8-3544-43e9-a074-98f6ee9795c3.png) I am getting the above error while following the installation instruction.

Related to #390. Fix environment variable generation for `fnm env` in Windows. Cygwin, MSYS, and Git Bash use UNIX-style paths (like `/c/Users/username/AppData/Local/fnm_multishells`), but fnm generates Windows-style paths (like `C:\Users\username\AppData\Local\fnm_multishells`) in...

PR: Bugfix
os:windows

I've installed `fnm` on mac using homebrew, and put `eval "$(fnm env)"` inside my `.zshrc`. It appears to work, but when I run `fnm use `, and test that version...

Since wsl can invoke commands on Windows, I tried to use fnm on wsl. Follow the instructions and add the following to `.bashrc` ``` eval "$(fnm.exe env --use-on-cd)" ``` Then...

os:windows

Now that nushell has an eval-like mechanism for setting environment variables, Iā€™d like to open this feature request to also add support for it. Via the `load-env` command, one can...

enhancement

When executing most any fnm command, I've started getting this error: ``` āÆ fnm list-remote thread 'main' panicked at 'Client::new(): reqwest::Error { kind: Builder, source: Custom { kind: Other, error:...

The setup for Git Bash (Windows) cannot run cli tools that are installed using `npm install -g`. ``` $ fnm env export PATH="C:\\Users\\XXX\\AppData\\Local\\Temp\\fnm_multishell_15584_1612875966568":$PATH export FNM_MULTISHELL_PATH="C:\\Users\\XXX\\AppData\\Local\\Temp\\fnm_multishell_15584_1612875966568" ... ``` Running node works:...