next.js: Dev compiling is stuck
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 18.15.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 13.2.4
eslint-config-next: 13.2.4
react: 18.2.0
react-dom: 18.2.0
warn - Latest canary version not detected, detected: "13.2.4", newest: "13.2.5-canary.26".
Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
Read more - https://nextjs.org/docs/messages/opening-an-issue
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true)
Link to the code that reproduces this issue
.
To Reproduce
Describe the Bug
in enabled app directory next js app, if i start development mode, compiler is stuck (npm run dev). Showing message: wait - compiling /page (client and server)… . Sometime works, sometimes doesn’t work.
Expected Behavior
Only it’s work
Which browser are you using? (if relevant)
Chrome latest
How are you deploying your application? (if relevant)
next start
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 4
- Comments: 21
i’m having this error too!. seems almost everyone is having this same error. is there a sure fix?
So this is what’s working for me now. I’ve added
--turbo
flag toscripts.dev
inpackage.json
.So far
npm run build
is still not compiling on my computer but at least it’s working in the Bitbucket pipelines. Would be perfect if I would be able to build it locally as well.I found that we need to open http://localhost:3000/ it in any of the browser for the rest of the compilation to work.
please try ot out and close this issue if it got resolved.
same problems with 14.1.0/14.1.1 and latest canary compilation hangs when I try to access any app-router based page (typescript 5.3.3)
having the same issue -
"next": "^14.1.4"
withnext@canary
installedmy problem was tailwind config.
In my experience, starting
http://localhost:3000/
, or your port, is necessary for Next.js to finish compilingTo solve this issue, just install latest version 13.2.5-canary.27. Type like this in terminal -
npm install next@13.2.5-canary.27
that’s it.He is using that version already, try installing latest canary version …27 will probably resolve.
For me it was
"next": "canary"
that was causing a new similar bug just now.Reverting to
"next": "13.2.4"
fixed it for me.