national-gold•6mo ago

Error while trying to run a new refine app

I created a new app with npm create refine-app@latest using antd and rest api , But it is throwing me this error when I try to run npm run start [Error: ENOENT: no such file or directory, open 'D:\Personal-Projects\Web Projects\16 Mega Projects\portfolio-v8.next\BUILD_ID'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'D:\Personal-Projects\Web Projects\16 Mega Projects\portfolio-v8\.next\BUILD_ID' }

5 Replies

kapa.ai•6mo ago

Hi @I_paid_for_winrar. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Hmm, I don't know enough to give you a confident answer yet. However, the error message suggests that the file 'BUILD_ID' in the '.next' directory cannot be found. This could be due to several reasons such as the build process not completing successfully, or the '.next' directory being deleted or not generated. You can try to delete the '.next' directory and the 'node_modules' directory and then reinstall the dependencies and run the build again:

rm -rf .next node_modules
npm install
npm run build
npm run start

rm -rf .next node_modules
npm install
npm run build
npm run start

If the problem persists, it might be a bug or an issue with your specific setup. In that case, you might want to check the refine GitHub issues (https://github.com/refinedev/refine/issues) to see if anyone else has encountered a similar problem or to report a new issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•6mo ago

<@859735059942735892> kapa.ai is still learning and improving, please let us know how it did by reacting below

generous-apricot•6mo ago

Hello @I_paid_for_winrar, kapa.ai answer is seems good. did you try it ?

national-gold•6mo ago

Yes I did but it created a .next folder but even after that running the app is showing me the same error

generous-apricot•6mo ago

I believe reinstalling node lts version can be helpfull