Getting similar errors:
Export encountered errors on following paths:
/_not-found

Also getting this error:

Generating static pages (0/24) [ ]Error: Could not find the module "C:\path\to\project\node_modules\next\dist\client\components\error-boundary.js#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at ek (C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:12617)
at C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:24131
at Object.toJSON (C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:25224)
at stringify (<anonymous>)
at eT (C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:13686)
at eP (C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:14212)
at Timeout._onTimeout (C:\path\to\project\node_modules\next\dist\compiled\next-server\app-page.runtime.prod.js:91:12034)
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)

Most of my routes are dynamic. But its still trying to render a few components on build time thats inside the layout.tsx. But since I dont have the tokens etc for connecting to my BE under build, im getting a lot for 401 as well.

Just Updated from next@13.4.19 to next@13.5.4

Same here, with _not-found.

This is very weird every new project I initialize without coding anything and then build it throws error, but at some computers it does not

Different os or node version? Im on sonoma Mac OS

Im have error with importing modules from next@babel….. dont know for you

can you call the next info command and put it here for a working pc and a non working pc? maybe we can work out what the difference is

alright

I checked and only difference is node versions

I installed same version but I get same error lol very weird

Very helpful thanks guys! 🤦‍♂️

I have the same issue