-
Notifications
You must be signed in to change notification settings - Fork 290
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
Trouble creating a hydrogen project on Windows 11 #2578
Comments
Thanks for the report @joelschout Can you confirm you've got additional tools installed? |
I did not, they are installing. I will try again after they are finished. |
i have installed it, still the same error and issue |
I am getting the same issue. Any thoughts? |
How has this still not been fixed? |
I am still getting the same issue |
**Hi, I see a similar issue on Windows 11 Pro when running both:
The error below led me to try installing under a different user, but the issue persists. The username does contain space input example name below. Steps to Reproduce
Error Message
Any ideas on how to resolve this? |
What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
latest
What version of Remix are you using?
No response
Steps to Reproduce
i run the command npm create @shopify/hydrogen@latest -- --quickstart in a project folder on C:\Users{your-user-name}\OneDrive\Documents\Projetct\Shopify and got an error.
i have installed node 20.17.0
Expected Behavior
i expected to install the project without any problems, i tried it on a windows 10 pc and i had no problems with it
Actual Behavior
it got me this error:
npm error code 1
npm error path C:\Users\username\OneDrive\Documents\Projects
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c create-hydrogen --quickstart
npm error A complete log of this run can be found in: C:\Users\username\AppData\Local\npm-cache_logs\2024-09-30T17_50_20_244Z-debug-0.log
The text was updated successfully, but these errors were encountered: