wierd error
Answered
American black bear posted this in #help-forum
American black bearOP
so, my app was working normally, no problems, today when i tried to run npm run dev (i didnt change anything just run it) i got this wierd error, that even the terminal wasnt enough to fit it , anyone have any idea ?
https://gist.github.com/Enkai0110/2336a8fe345f17cdd0221c4661a19785
https://gist.github.com/Enkai0110/2336a8fe345f17cdd0221c4661a19785
Answered by Orinoco Crocodile
In one instance, it's looking in
Notice the difference in lower case versus upper case d in development/Development.
This might be a good reference for fixing it:
https://github.com/vercel/next.js/issues/10739
E:\development\gero... and the other one it's looking in E:\Development\gero....Notice the difference in lower case versus upper case d in development/Development.
This might be a good reference for fixing it:
https://github.com/vercel/next.js/issues/10739
6 Replies
Orinoco Crocodile
Is it possible that you changed your default path?
Orinoco Crocodile
In one instance, it's looking in
Notice the difference in lower case versus upper case d in development/Development.
This might be a good reference for fixing it:
https://github.com/vercel/next.js/issues/10739
E:\development\gero... and the other one it's looking in E:\Development\gero....Notice the difference in lower case versus upper case d in development/Development.
This might be a good reference for fixing it:
https://github.com/vercel/next.js/issues/10739
Answer
@Orinoco Crocodile Is it possible that you changed your default path?
American black bearOP
bro i owe you my life ;-; it worked
im kinda a bad error reader, can i ask which part made you identify the problem ?
@American black bear im kinda a bad error reader, can i ask which part made you identify the problem ?
Orinoco Crocodile
Hey! Glad that it worked out for you. I just googled the error message and went through the available results on Stack Overflow and Github.
Orinoco Crocodile
I went back through my history and this was the search query that finally lead me to good results:
As you can see, the second result was already the helpful one here.
react-refresh-utils There are multiple modules with names that only differ in casing.As you can see, the second result was already the helpful one here.