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

npm run dev does not run, shows this error #5515

Closed
SaiRev0 opened this issue May 24, 2023 · 11 comments
Closed

npm run dev does not run, shows this error #5515

SaiRev0 opened this issue May 24, 2023 · 11 comments

Comments

@SaiRev0
Copy link

SaiRev0 commented May 24, 2023

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

I ran npm install --legacy-peer-deps
Then run npm run dev
It shows this error

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • Windows 11

Additional context
Using vs-code and GitBash Terminal

@rithviknishad
Copy link
Member

I'm not sure if it's because your working directory path has spaces in it. I don't have a windows machine to test it. Could you retry in a working directory without spaces in the path?

@skks1212 any idea?

@skks1212
Copy link
Member

skks1212 commented May 25, 2023

@SaiRev0 can you check if your project folder name contains spaces? If so, please remove the spaces and try again.

Reference: https://stackoverflow.com/a/73204282

@divyanshkhetan
Copy link
Contributor

@rithviknishad I had the same issue, moving the repo to a directory with no spaces helped me solve it.

@MayaSatishRao
Copy link
Contributor

@divyanshkhetan @rithviknishad I have the project in a directory whose name has no spaces. Still it is not working. Could you help?
Screenshot 2023-05-25 172434

@rithviknishad
Copy link
Member

Did you run npm install --legacy-peer-deps before that?

@sainak
Copy link
Member

sainak commented May 25, 2023

@SaiRev0 @MayaSatishRao it's recommended to use a unix environment for developing care.
Can you try running the project in wsl.

@MayaSatishRao
Copy link
Contributor

@rithviknishad I did. Do I need wsl as recommended by @sainak ?

@rithviknishad
Copy link
Member

It's best if you could do it in WSL

@MayaSatishRao
Copy link
Contributor

ok

@SaiRev0
Copy link
Author

SaiRev0 commented May 25, 2023

@SaiRev0 @MayaSatishRao it's recommended to use a unix environment for developing care. Can you try running the project in wsl.

Thanks a lot for sharing, I m having a dual boot setup so I can directly work on Ubuntu

@MayaSatishRao
Copy link
Contributor

I got the project running in my system and here is what I did:

  1. run npm cache clean --force
  2. Update the node version to 18.16.0 and npm version to 9.6.7(current latest ersions)
  3. run npm install --legacy-peer-deps
  4. run npm run dev

I updated the node version because I found this: https://github.com/vitejs/vite/issues/9113#issuecomment-1184319357

@rithviknishad rithviknishad closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2023
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

6 participants