next.js: `next dev` and `next build` broken on Yarn PnP in the latest release

What version of Next.js are you using?

v12.0.5

What version of Node.js are you using?

v16.13.1

What browser are you using?

N/A

What operating system are you using?

Windows 11 (Build 22509.1000)

How are you deploying your application?

yarn next build && yarn next start

Describe the Bug

Getting the following errors on running yarn next build:

$ yarn next build
info  - Checking validity of types
warn  - No ESLint configuration detected. Run next lint to begin setup
info  - Creating an optimized production build
Failed to compile.

./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/index.js
Error: Failed to read source code from C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\client\index.js

Caused by:
    The system cannot find the path specified. (os error 3)

Import trace for requested module:
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/next.js

./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/request-idle-callback.js
Error: Failed to read source code from C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\client\request-idle-callback.js

Caused by:
    The system cannot find the path specified. (os error 3)

Import trace for requested module:
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/route-loader.js
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/shared/lib/router/router.js
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/router.js

./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/pages/_app.js
Error: Failed to read source code from C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\pages\_app.js

Caused by:
    The system cannot find the path specified. (os error 3)

./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/shared/lib/head.js
Error: Failed to read source code from C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\shared\lib\head.js

Caused by:
    The system cannot find the path specified. (os error 3)

Import trace for requested module:
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/pages/_error.js

./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/shared/lib/mitt.js
Error: Failed to read source code from C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\shared\lib\mitt.js

Caused by:
    The system cannot find the path specified. (os error 3)

Import trace for requested module:
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/shared/lib/router/router.js
./.yarn/__virtual__/next-virtual-fedb67b0ce/0/cache/next-npm-12.0.5-1c991f073c-616235e394.zip/node_modules/next/dist/client/router.js


> Build failed because of webpack errors

The issue seems to be SWC related. After creating .babelrc with next/babel preset, the yarn next build command is working but yarn next dev is still throwing error.

Also, why the Checking validity of types log is shown even if someone is not using TS?

Expected Behavior

To build successfully and start as happens in next@12.0.4.

To Reproduce

mkdir foo && cd "$_"
yarn init -2
yarn add next react react-dom
mkdir pages
echo 'export default () => <div>Hello World</div>' > pages/index.js
yarn next build

Based on https://github.com/yarnpkg/berry/blob/master/.github/workflows/e2e-next-workflow.yml

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 38
  • Comments: 19 (6 by maintainers)

Commits related to this issue

Most upvoted comments

@timneutkens next build is working after setting that, but next dev is still throwing errors:

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
warn  - You have enabled experimental feature(s).
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.

error - ./.yarn/__virtual__/react-dom-virtual-7a7367685f/0/cache/react-dom-npm-17.0.2-f551215af1-1c1eaa3bca.zip/node_modules/react-dom/cjs/react-dom.development.js
Module build failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received type number (-2147483514)
    at new Promise (<anonymous>)
wait  - compiling...
error - ./.yarn/__virtual__/react-dom-virtual-7a7367685f/0/cache/react-dom-npm-17.0.2-f551215af1-1c1eaa3bca.zip/node_modules/react-dom/cjs/react-dom.development.js
Module build failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received type number (-2147483418)
    at new Promise (<anonymous>)
wait  - compiling...
error - ./.yarn/__virtual__/react-dom-virtual-7a7367685f/0/cache/react-dom-npm-17.0.2-f551215af1-1c1eaa3bca.zip/node_modules/react-dom/cjs/react-dom.development.js
Module build failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received type number (-2147483418)
    at new Promise (<anonymous>)
(node:13216) [DEP_WEBPACK_MODULE_ISSUER] DeprecationWarning: Module.issuer: Use new ModuleGraph API
(Use `node --trace-deprecation ...` to show where the warning was created)
wait  - compiling /_error (client and server)...
error - ./.yarn/__virtual__/react-dom-virtual-7a7367685f/0/cache/react-dom-npm-17.0.2-f551215af1-1c1eaa3bca.zip/node_modules/react-dom/cjs/react-dom.development.js
Module build failed: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received type number (-2147483418)
    at new Promise (<anonymous>)
error - Error: Qualified path resolution failed - none of those files can be found on the disk.

Source path: C:\Users\brc-dd\Desktop\foo\.next\fallback-build-manifest.json
Not found: C:\Users\brc-dd\Desktop\foo\.next\fallback-build-manifest.json
Not found: C:\Users\brc-dd\Desktop\foo\.next\fallback-build-manifest.json.js
Not found: C:\Users\brc-dd\Desktop\foo\.next\fallback-build-manifest.json.json
Not found: C:\Users\brc-dd\Desktop\foo\.next\fallback-build-manifest.json.node

Require stack:
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\load-components.js
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\build\utils.js
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\build\output\store.js
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\build\output\index.js
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\cli\next-dev.js
- C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\bin\next
    at Function.external_module_.Module._resolveFilename (C:\Users\brc-dd\Desktop\foo\.pnp.cjs:13363:55)
    at Function.mod._resolveFilename (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\build\webpack\require-hook.js:171:28)
    at Function.external_module_.Module._load (C:\Users\brc-dd\Desktop\foo\.pnp.cjs:13162:48)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.loadDefaultErrorComponents (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\load-components.js:22:24)
    at DevServer.getFallbackErrorComponents (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\dev\next-dev-server.js:679:43)
    at async DevServer.renderErrorToResponse (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\next-server.js:1738:40)
    at async pipe.req.req (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\next-server.js:1678:30)
    at async DevServer.pipe (C:\Users\brc-dd\Desktop\foo\.yarn\__virtual__\next-virtual-fedb67b0ce\0\cache\next-npm-12.0.5-1c991f073c-616235e394.zip\node_modules\next\dist\server\next-server.js:1156:25)

PS: This is happening since v12.0.5-canary.0.

Related Issues - #31552, #31812

+15
brc-dd on Dec 5, 2021

This prevents me from using Next.js >= v12.0.5.

Edit: node v16.13.1, macOS 12.0.1

+12
dlindenkreuz on Dec 13, 2021

@dgattey that option has been recently changed to accommodate your use case in #33236 we will include it in the next upcoming canary release (which is 🔜™️), thanks for the feedback! 👍

+7
balazsorban44 on Jan 18, 2022

Version 12.0.4 is the highest version I could go without this error.

+4
kaptcha0 on Dec 22, 2021

For now, if anyone is facing the issue with next dev, try unplugging react-dom (yarn unplug react-dom), it should work (although in a way this defeats the purpose of zero-installs).

+2
brc-dd on Dec 13, 2021

@taavisalo Have you added swcFileReading: false, to experimental? Setting it in the root object doesn’t work, but in experimental I was able to fix this issue.

+1
amuttsch on Jan 12, 2022

Still broken with latest 12.0.8. yarn dev throws “Failed to read source code” errors.

@taavisalo see here: #32867 (comment)

Thank you! Running yarn cache clear fixed the problem.

EDIT: yarn dev works, but yarn build still fails with “Error: Failed to read source code” errors.

+1
taavisalo on Jan 12, 2022

Still broken with latest 12.0.8. yarn dev throws “Failed to read source code” errors.

@taavisalo see here: https://github.com/vercel/next.js/pull/32867#issuecomment-1010860894

+1
kaykdm on Jan 12, 2022

@timneutkens @sokra

next build is working after setting that, but next dev is still throwing errors:

I just opened PR to fix this https://github.com/vercel/next.js/pull/32867

+1
kaykdm on Dec 28, 2021

@brc-dd Thanks for the hint, unplugging react query “fixes” my error above. But I agree, unplugging should not be the solution for this issue. I’m staying on 12.0.5 for now until we have a proper fix 😃

+1
amuttsch on Dec 13, 2021
Read more comments on GitHub
← next.js: `next build` fails with webpack error
next.js: next dev bug: ReferenceError: performance is not defined →