-
Notifications
You must be signed in to change notification settings - Fork 403
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
Add powershell script for installation on windows #1018
base: master
Are you sure you want to change the base?
Conversation
|
First of all, I'd like to thank you for the time and effort and making the hard thing possible and contributing! However, in my opinion, any installation script is a toll and out of this project scope, and I originally built the installation script to ease the installation process and it only makes sense for Linux nowadays. Since Windows has WinGet baked in as a standard installation mechanism, I don't really see the point in having a custom PowerShell installer. Do you? can you please explain why should we have an installation script and not offload to WinGet? |
ig stuff like scoop and winget does exist which allows people to install fnm. But i dont think everyone uses them. Winget is certainly popular but its yet to be used by everyone, while powershell is always there in windows and a one liner script can just be used to quickly do installations. package managers are great but you wouldnt install one just to get a single app. the script itself wasnt much work, if u wanna use it, sure. if not then its all good. |
Hi @Yakiyo, I would like to install fnm under Also, since the bash script install fnm under Am I missing something? |
Actually default was changed a while ago and now bash script prefers See https://github.com/Schniz/fnm/blob/master/.ci/install.sh#L8-L16 |
Okay, now it is clear; I based my previous sentence on the README file without opening the actual scripts. |
This adds a powershell script for installing fnm on windows. The ps script tries to follow the bash script as much as possible. Supported flags are:
Using only one
-
seems odd to me but thats how powershell parses arguments. As far as i've tested, it even works with only the first argument too, as in-version
,-v
and-V
all do the same thing.To install fnm via the script, users would do
The bash script uses the
install
endpoint, the ps script could do ighttps://fnm.vercel.app/install.ps
or something.I've tested the script a few times and ensured that it works.