App Router Producing Errors on Fresh Build (13.4.10 and other versions)
Unanswered
Somali posted this in #help-forum
SomaliOP
Upon creating a new app with
(See image)
Also, in the console for localhost:3000:
(Note the path for Documents and udemy_next are appended together, which seems incorrect.
This also seems to have been experienced by others:
https://github.com/vercel/next.js/issues/52817
https://stackoverflow.com/questions/76244354/while-selecting-app-router-yes-in-next-js-13-while-installing-through-npx-crea/76725424#76725424
Though no clear answer seems to exist.
This error doesn't occur when selecting to NOT use the app router.
Running up to date Windows 11, Node v18.17.0, npm v9.8.0
npx create-next-app@latest, running npm run dev produces the following errors:(See image)
Also, in the console for localhost:3000:
(Note the path for Documents and udemy_next are appended together, which seems incorrect.
Uncaught Error: Could not find the module "C:\Users\MyUsername\Documentsudemy_next\my_app\node_modules\next\dist\client\components\app-router.js#default" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
at resolveClientReferenceMetadata (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:327:27)
at serializeClientReference (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:1510:47)
(truncated for length)
server.edge.development.js:1429:28)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)This also seems to have been experienced by others:
https://github.com/vercel/next.js/issues/52817
https://stackoverflow.com/questions/76244354/while-selecting-app-router-yes-in-next-js-13-while-installing-through-npx-crea/76725424#76725424
Though no clear answer seems to exist.
This error doesn't occur when selecting to NOT use the app router.
Running up to date Windows 11, Node v18.17.0, npm v9.8.0