Urgent Help - Unable to view my React Project when I perform npm run dev #15108
-
|
When I run npm run dev this error keeps appearing node:internal/modules/cjs/loader:1473 Error: The specified module could not be found. Node.js v21.2.0 |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 18 replies
-
|
You'll need to provide a proper reproduction, you can use https://vite.new for example to generate it. Just in case, did you run |
Beta Was this translation helpful? Give feedback.
-
|
I also redid creating React with Vite on the Visual Studio Terminal same error. I've attached an image illustrating the information I entered and the resulting error. |
Beta Was this translation helpful? Give feedback.
-
|
Could you run I see another user with the same issue at https://stackoverflow.com/questions/77526066/error-when-running-the-command-line-npm-run-dev-in-a-vite-project-of-the-lates. And there was also a report in Discord. I was going to recommend trying out using pnpm or a different version of node, but in the linked question above they already tried. It would be good to test though. It is an issue with Rollup 4 (which now is distributed with binaries) and Windows (@sapphi-red did you see this before?). Until this is fixed, you can switch to Vite 4 (npm create vite@4, or update your current project to vite@4.5.0) |
Beta Was this translation helpful? Give feedback.
-
|
I think you may be hitting this issue (cc @Tr1ckyy1 too): |
Beta Was this translation helpful? Give feedback.
-
|
@Nestor-Max @Tr1ckyy1 your problem may actually be solved following these steps: lerna/lerna#3612 (comment) This worked for someone on Discord that had the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @patak-dev, I wanted to update you that following your suggestion, I switched to Vite 4 (using npm create vite@4 or vite@4.5.0), and it seems to be working. Your prompt response and guidance are greatly appreciated. If there's an opportunity for me to contribute to user testing when the Rollup 4 issue is resolved or any other aspect, I am available and eager to help and contribute as a new member to this community. Once again, thank you for your assistance. You're awesome! |
Beta Was this translation helpful? Give feedback.
-
|
It once happened to me. Running |
Beta Was this translation helpful? Give feedback.
-
|
I found the reason why it happened in my case. The reason was npm/cli#4828. |
Beta Was this translation helpful? Give feedback.
-
|
Made a PR to rollup: rollup/rollup#5267 |
Beta Was this translation helpful? Give feedback.
-
|
This is the same exact issue that i've been getting for the past 2 days, both on node and VScode Terminal. I've found some solutions to it on the internet but none of them have worked for me so far... |
Beta Was this translation helpful? Give feedback.
-
|
@Tr1ckyy1 Thank you for commenting on this issue, it was seeming like I was the only one with this issue in the ViteJs ecosystem. I even formatted my entire system. I have been on it all night. Please can anyone help, we can not do any work at all |
Beta Was this translation helpful? Give feedback.
-
|
I have similar issue too and i dont know how to fix it |
Beta Was this translation helpful? Give feedback.
-
|
bless ya.... working now |
Beta Was this translation helpful? Give feedback.
-
|
https://aka.ms/vs/17/release/vc_redist.x64.exe I install this too and it works after 2 days thanks guys and how it works? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks buddy, It worked for me😊🤝😇 |
Beta Was this translation helpful? Give feedback.
-
|
I faced the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
I also faced same problem while running command "npm run dev" , https://aka.ms/vs/17/release/vc_redist.x64.exe I install this too and it works for me. |
Beta Was this translation helpful? Give feedback.
-
|
it's working fine. thankyou @khadijafatima409 |
Beta Was this translation helpful? Give feedback.
@Nestor-Max @Tr1ckyy1 your problem may actually be solved following these steps: lerna/lerna#3612 (comment)
This worked for someone on Discord that had the same issue.