-
Notifications
You must be signed in to change notification settings - Fork 527
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
Windows install did not add PATH environment after installed node.
#1410
opened Apr 8, 2025 by
amnuaym
Using fnm to launch MCP server in Visual Studio Code using specific node version fails
#1406
opened Apr 2, 2025 by
jessehouwing
[Question] Why every time I open a terminal a new folder is added inside the fnm_multishells folder
#1392
opened Mar 8, 2025 by
kallookoo
Option to update and/or remove Corepack inside Node.js installation
#1378
opened Feb 6, 2025 by
o-l-a-v
Installing fnm on macOS using recommended script & Brew sets incorrect path
#1376
opened Feb 4, 2025 by
Mathias-S
--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
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.