Open kirill-konshin opened 1 year ago
Any update on here??
Same issue.
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
App directory (appDir: true)
Link to the code that reproduces this issue
https://codesandbox.io/s/next-webpack-async-iy1bn4?file=/next.config.js
To Reproduce
Run
next build
Describe the Bug
Build fails with
Also I managed to get another error locally (not in sandbox):
I've patched the
next/dist/build/index.js
like so:And here's the outcome:
As you see,
clientEntry
does not havemain-app
.The workaround is not to use async webpack config.
Expected Behavior
Should work with async webpack config.
Which browser are you using? (if relevant)
Chrome, irrelevant
How are you deploying your application? (if relevant)
next build && next start