Open dgrimaldi-intellyse opened 3 months ago
I have also encountered this issue.
Using --turbo seems mitigate the issue, at least in local
Using --turbo seems mitigate the issue, at least in local
Thanks for the info, I will try at home. Hopefully they fix the root cause soon.
Using --turbo seems mitigate the issue, at least in local
I can agree it mitigates the issue on v14.1.3
Having the same issue with Tailwind Template: Studio. Confirmed testing with --turbo seems to mitigate...
Same issue on node v20.16.0 and Next v14.2.5
Where do you use --turbo as a workaround ? On start command ?
Same issue on node v20.16.0 and Next v14.2.5
Where do you use --turbo as a workaround ? On start command ?
In the package.json at dev command
"dev": "next dev --turbo",
Link to the code that reproduces this issue
https://github.com/Intellyse/next-js-bug
To Reproduce
Current vs. Expected behavior
Provide environment information
Which area(s) are affected? (Select all that apply)
Webpack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
The error seems happen randomly, and we have this issue also in production. It seems related with something with webpack
the error rise at line: var error = new Error();