-
Notifications
You must be signed in to change notification settings - Fork 495
Issues: Schniz/fnm
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
--resolve-engines in combination with --use-on-cd for cmd/cmder does not seem to work
#1372
opened Jan 22, 2025 by
nicklastromb
fnm multishell makes it unable to run npx MCP server in Claude Desktop
#1366
opened Jan 13, 2025 by
piavgh
The package installs on ARM Raspberry, but will not run since it is not an ARM executable
#1360
opened Jan 3, 2025 by
Darker
Make "fnm" an official installation method for Node.js on Windows
#1357
opened Dec 28, 2024 by
ovflowd
Use existing
cd
alias in the script that fnm env --shell powershell --use-on-cd
emits
#1350
opened Dec 25, 2024 by
ravindUwU
resolve-engines / FNM_RESOLVE_ENGINES always chooses latest instead of current
#1339
opened Dec 1, 2024 by
jakebailey
Non-interactive
fnm use
-- avoid prompting to install version
#1333
opened Nov 22, 2024 by
philipmat
When resizing the VS Code terminal fnm spams 'Can't infer shell' errors
#1329
opened Nov 17, 2024 by
efindus
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.