Skip to content
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

Install node.js v22.12.0 failed use powershell with unknown problem. #7363

Closed
djx314 opened this issue Dec 27, 2024 · 5 comments
Closed

Install node.js v22.12.0 failed use powershell with unknown problem. #7363

djx314 opened this issue Dec 27, 2024 · 5 comments

Comments

@djx314
Copy link

djx314 commented Dec 27, 2024

System: Windows x64
Use the command in nodejs.org to install node.js v22.12.0, and call unknown exception in powershell.

Image

Windows PowerShell
版权所有(C) Microsoft Corporation。保留所有权利。

安装最新的 PowerShell,了解新功能和改进!https://aka.ms/PSWindows

PS D:\f\tools>
PS D:\f\tools>
PS D:\f\tools> # installs fnm (Fast Node Manager)
PS D:\f\tools> curl -fsSL https://fnm.vercel.app/install | bash
bash : 无法将bash项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写,如果包括路径,请确保路径正确
,然后再试一次。
所在位置 行:1 字符: 45
+ curl -fsSL https://fnm.vercel.app/install | bash
+                                             ~~~~
    + CategoryInfo          : ObjectNotFound: (bash:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

PS D:\f\tools>
PS D:\f\tools>
@ljharb
Copy link
Member

ljharb commented Dec 28, 2024

Whoops, when I restored the preambles in #7360 i didn't realize fnm had windows-specific install instructions (winget install Schniz.fnm and then fnm env --use-on-cd | Out-String | Invoke-Expression instead of the first two lines that are currently there). I'll see if I can fix it.

@ljharb
Copy link
Member

ljharb commented Dec 28, 2024

It's also possible that #7357 will fix this.

@ljharb
Copy link
Member

ljharb commented Dec 28, 2024

I believe #7357 has indeed fixed it. Please comment if not, and I'll be sure to reopen.

@ljharb ljharb closed this as completed Dec 28, 2024
@djx314
Copy link
Author

djx314 commented Dec 28, 2024

I believe #7357 has indeed fixed it. Please comment if not, and I'll be sure to reopen.

@ljharb Yes, problem with (Windows + fnm) is already fixed.

@ovflowd
Copy link
Member

ovflowd commented Dec 28, 2024

Awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants