Unknown error in dev mode
Answered
Japanese Bobtail posted this in #help-forum
Japanese BobtailOP
[Error: UNKNOWN: unknown error, open 'G:\Projects\Web-Development\college\employee-management\client\.next\static\chunks\app\page.js'] {
errno: -4094,
code: 'UNKNOWN',
syscall: 'open',
path: 'G:\\Projects\\Web-Development\\college\\employee-management\\client\\.next\\static\\chunks\\app\\page.js'
}
I get this error everytime I use dev mode. I don't know how to fix it. Somtimes it workes perfectly on a different machine but not mine.
Answered by James4u
you can say it's a bug but as it's not production build - while running your project on your local - those errors come from any of your chunk js - which gets updated everytime you update your codebase meaning it's a bit understandable
41 Replies
@Japanese Bobtail If you re-run your project, it should be gone away I think
@James4u <@707107037070360596> If you re-run your project, it should be gone away I think
Japanese BobtailOP
sometimes, but not everytime
what do you mean by everytime?
you get this error everytime you visit a certain page?
Japanese BobtailOP
no
sometimes this error won't go away for hours
even the components are completely correct
yeah, when you encounter this error, simply rerun your project
@James4u yeah, when you encounter this error, simply rerun your project
Japanese BobtailOP
is this a next bug
you can say it's a bug but as it's not production build - while running your project on your local - those errors come from any of your chunk js - which gets updated everytime you update your codebase meaning it's a bit understandable
Answer
simply re-run your project, that's all
it won't happen in the production build
@James4u it won't happen in the production build
Japanese BobtailOP
I don't really need the current project for production
it's just for a college project
by production, I meant
npm run build & npm run start
Japanese BobtailOP
yes, I am aware
@Japanese Bobtail I don't really need the current project for production
what's the reason you think you don't need produciton build but just
npm run dev
???@James4u what's the reason you think you don't need produciton build but just `npm run dev`???
Japanese BobtailOP
I just want to work on it fast, I don't have to give a preview
some ss are enough ig
Japanese BobtailOP
yeah, that's what I said lol
I just meant you won't get those errors when you host your website
with production build
@James4u with production build
Japanese BobtailOP
okie
I hosted a client website a few months back
it's working great
they love it
yeah, so if you encounter the error while developing, just restart the server
that's all
and @Japanese Bobtail mark solution if you don't have any questions and if it helped you!
Japanese BobtailOP
ok
@James4u yeah, so if you encounter the error while developing, just restart the server
Japanese BobtailOP
fkk
same error
just restarted
remove
.dist
and restart - give it a try!Japanese BobtailOP
I just remove entire .next lol
oh yeah, I meant build output folder
@James4u oh yeah, I meant build output folder
Japanese BobtailOP
man the errors are getting really frequent