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
Cannot create react-app in WSL #5669
Comments
Bun is currently a hot trend so there will be many people using it and can be used for production so there will be a lot of issues so hopefully bun will be even stronger in the future. |
I think I had the same issue once, but it wasn't related to Bun. As long as you create your projects inside your WSL directories and the I tried to reproduce your error, but didn't have any problems as I ran Thus, try to run Hope it helps ! |
The issue is not that, the issue is bun is starting npm in windows path and not Linux path so npm fails because current path (linux) doesn't match the path it was told (the windows path) |
Ok, then where is located your
|
Any update @patr543a ? |
This is what i get |
Okay, I'm pretty sure the problem lie in your Node installation on your WSL because This thread can also help you : microsoft/WSL#1896 |
@patr543a I am having the same exact issue in my vscode WSL terminal. Did you ever fix your problem? |
What version of Bun is running?
1.0.2+37edd5a6e389265738e89265bcbdf2999cb81a49
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What steps can reproduce the bug?
bun create react-app reactAppName
What is the expected behavior?
It creates the app without any errors
What do you see instead?
I get an error that says:
Could not start an npm process in the right directory.
The current directory is: /mnt/c/Users/pathToFolder/reactAppName
However, a newly started npm process runs in: C:\Users\pathToFolder\reactAppName
This is probably caused by a misconfigured system terminal shell.
error: "create-react-app" exited with code 1 (SIGHUP)
Additional information
the termial is at a different path in wsl than what it's trying to access, the final location is the same due to how wsl works but the result is that npm thinks it's different causing issues.
The text was updated successfully, but these errors were encountered: