Error: Failed to read source code from `amp-dev.js` #31812

rtritto · 2021-11-25T20:57:45Z

What version of Next.js are you using?

12.0.5-canary.10-12.0.8

What version of Node.js are you using?

14.17.0

What browser are you using?

Not relevant

What operating system are you using?

Windows

How are you deploying your application?

Not relevant

Describe the Bug

I updated next.js from v12.0.5-canary.9 to v12.0.5-canary.10 and I got a file not found error of amp-dev.js.

Expected Behavior

No error.

To Reproduce

yarn init -y
yarn set version canary
yarn add next@canary react react-dom
Create pages folder
yarn next
Read log:

(node:14180) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - ./.yarn/__virtual__/next-virtual-553eee263b/0/cache/next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip/node_modules/next/dist/client/dev/amp-dev.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-553eee263b\0\cache\next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip\node_modules\next\dist\client\dev\amp-dev.js       

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-553eee263b/0/cache/next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip/node_modules/next/dist/client/dev/amp-dev.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-553eee263b\0\cache\next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip\node_modules\next\dist\client\dev\amp-dev.js       

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-553eee263b/0/cache/next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip/node_modules/next/dist/client/dev/amp-dev.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-553eee263b\0\cache\next-npm-12.0.5-canary.10-1a75536391-cbd811bead.zip\node_modules\next\dist\client\dev\amp-dev.js       

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

The text was updated successfully, but these errors were encountered:

rtritto · 2021-11-25T21:09:46Z

It should depend on changes in #31772 or #31759.

Edit:
I did a log of:

next.js/packages/next/build/webpack-config.ts

Line 502 in b2acdbb

const clientEntries = !isServer

next.js v12.0.4 (correctly work):

clientEntries: {
  'main.js': [],
  'react-refresh': 'C:\\test-next\\.yarn\\__virtual__\\@next-react-refresh-utils-virtual-17b7e6438c\\0\\cache\\@next-react-refresh-utils-npm-12.0.4-d8661f51f6-7c1c9c3284.zip\\node_modules\\@next\\react-refresh-utils\\runtime.js',
  amp: './.yarn/__virtual__/next-virtual-f94b832183/0/cache/next-npm-12.0.4-fcbd6e5d3e-b9711e7d42.zip/node_modules/next/dist/client/dev/amp-dev',
  main: './.yarn/__virtual__/next-virtual-f94b832183/0/cache/next-npm-12.0.4-fcbd6e5d3e-b9711e7d42.zip/node_modules/next/dist/client/next-dev.js'
}

next.js v12.0.5-canary.11:

clientEntries: {
  'main.js': [],
  'react-refresh': 'C:\\test-next\\.yarn\\__virtual__\\@next-react-refresh-utils-virtual-a50cc4b923\\0\\cache\\@next-react-refresh-utils-npm-12.0.5-canary.11-d08910d2ba-2bab76619a.zip\\node_modules\\@next\\react-refresh-utils\\runtime.js',
  amp: './.yarn/__virtual__/next-virtual-1354126498/0/cache/next-npm-12.0.5-canary.11-e87fce5999-fdd462fb46.zip/node_modules/next/dist/client/dev/amp-dev',
  main: './.yarn/__virtual__/next-virtual-1354126498/0/cache/next-npm-12.0.5-canary.11-e87fce5999-fdd462fb46.zip/node_modules/next/dist/client/next-dev.js'
}

Both values are similar, so this issue shouldn't yarn side.

There is a way to debug, log and/or help?

FYI @sokra @timneutkens

timruiterkamp · 2021-11-30T08:52:19Z

@rtritto any update on this? I am running into the same issues right now

rtritto · 2021-11-30T08:58:04Z

Nothing

timruiterkamp · 2021-11-30T09:00:22Z

@rtritto Hmm that's a shame.. I upgraded to yarn 3.1 and therefore had to upgrade Next to 12 but with i am running into the same issues as you do now.

Did you not have this issue on v12.0.5-canary.9?

rtritto · 2021-11-30T09:13:48Z

This issue persists with all latest yarn versions (currently 3.1.1 and 3.2.0-rc.6)

Did you not have this issue on v12.0.5-canary.9?

Maybe it works (bug #31552 blocks compiling after this issue is solved)

timruiterkamp · 2021-11-30T09:17:02Z

I tried setting nodeLinker back to node-modules and that was a workaround. But also loading time went x100 because of that. So hopefully the fixes they are pushing will fix these issues so we can use yarn pnp :)

arcanis · 2021-12-01T16:24:20Z

I suspect this is caused by Next reading files on the wasm/rust side rather than JS. It means it doesn't go through the layer Yarn puts in place so that dependencies can be accessed directly from their zip archives.

The simplest fix preserving the intent would be for Next to fallback to using the fs.readFileSync method if it detects .yarn in the file path.

arcanis · 2021-12-01T17:04:05Z

This sounds like the problematic commit: #31682

cc @sokra

kachkaev · 2021-12-02T09:32:10Z

A reproduction can be found here: kachkaev/njt#161

The main branch of that repo uses Yarn 3.1.1 with nodeLinker: node-modules and Next.js 12.0.5-canary.13. Everything works. The above PR switches the project to PnP, which breaks next dev and next build. I tried downgrading Next to 12.0.4 and it worked again.

Preview release works for the PR, but that’s because of a workaround on the Vercel side.

rtritto · 2021-12-02T10:33:21Z

This issue, should be fixed with #31995 (already merged in canary branch).
Waiting release of next.js v12.0.5-canary.14 to test.

rtritto · 2021-12-02T21:58:09Z

In next.js v12.0.5-canary.14, it's fixed adding in next.config.js file:

module.exports = {
  ...
  experimental: {
    ...
    swcFileReading: false
  }
}

rtritto · 2021-12-02T22:03:49Z

Maybe this issue should remain opened because of experimental (temporary) fix.

kachkaev · 2021-12-02T22:26:52Z

I no longer see any mentions of amp-dev.js after upgrading to Next.js v12.0.5-canary.14 and enabling swcFileReading: false. However, #31552 is still there.

kachkaev · 2022-01-12T13:17:10Z

@rtritto could you try setting swcFileReading: false in next.config.js and upgrade to 12.0.8? The problem is probably resolved via #32867.

rtritto · 2022-01-12T13:43:33Z

Without swcFileReading: false, it still persists with random output errors:

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/amp-dev.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\amp-dev.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/webpack-hot-middleware-client.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\webpack-hot-middleware-client.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/webpack-hot-middleware-client.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\webpack-hot-middleware-client.js

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

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - ./.yarn/__virtual__/next-virtual-510b9827f9/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/amp-dev.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-510b9827f9\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\amp-dev.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-510b9827f9/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/index.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-510b9827f9\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\index.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-510b9827f9/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/index.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-510b9827f9\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\index.js

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

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/error-overlay/hot-dev-client.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\error-overlay\hot-dev-client.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/portal/index.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\portal\index.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/portal/index.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\portal\index.js

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

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/client/dev/error-overlay/format-webpack-messages.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\client\dev\error-overlay\format-webpack-messages.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/shared/lib/i18n/normalize-locale-path.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\shared\lib\i18n\normalize-locale-path.js

Caused by:
    The system cannot find the path specified. (os error 3)
wait  - compiling...
error - ./.yarn/__virtual__/next-virtual-c649e2e81d/0/cache/next-npm-12.0.8-aa55acca00-947f0295aa.zip/node_modules/next/dist/shared/lib/i18n/normalize-locale-path.js
Error: Failed to read source code from C:\test-nextjs\.yarn\__virtual__\next-virtual-c649e2e81d\0\cache\next-npm-12.0.8-aa55acca00-947f0295aa.zip\node_modules\next\dist\shared\lib\i18n\normalize-locale-path.js

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

I'm keeping this issue opened because of the temporary workaround with swcFileReading.

rtritto · 2022-01-13T01:24:34Z

This issue will be fixed with #33236

balazsorban44 · 2022-02-14T00:13:07Z

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

rtritto added the bug Issue was opened via the bug report template. label Nov 25, 2021

rtritto mentioned this issue Nov 25, 2021

The "path" argument must be of type string or an instance of Buffer or URL (react-dom) #31552

Closed

kachkaev mentioned this issue Dec 2, 2021

Yarn Berry: Switch from from node_modules to PnP kachkaev/njt#161

Merged

rtritto closed this as completed Dec 2, 2021

rtritto reopened this Dec 2, 2021

balazsorban44 added area: Yarn PnP / pnpm and removed bug Issue was opened via the bug report template. labels Dec 3, 2021

brc-dd mentioned this issue Dec 5, 2021

next dev and next build broken on Yarn PnP in the latest release #32115

Closed

rtritto mentioned this issue Dec 16, 2021

Next 12 Module Resolution broken for Yarn 2 PNP #32546

Closed

kaykdm mentioned this issue Dec 28, 2021

Fix broken yarn pnp #32867

Merged

10 tasks

balazsorban44 linked a pull request Jan 13, 2022 that will close this issue

Update yarn PnP tests and disable swc file reading for PnP #33236

Merged

3 tasks

ijjk mentioned this issue Jan 13, 2022

Update yarn PnP tests and disable swc file reading for PnP #33236

Merged

3 tasks

rtritto mentioned this issue Jan 13, 2022

yarn create next-app and run not work as expected #32721

Closed

ijjk closed this as completed in #33236 Jan 14, 2022

vercel locked as resolved and limited conversation to collaborators Feb 14, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Failed to read source code from `amp-dev.js` #31812

Error: Failed to read source code from `amp-dev.js` #31812

rtritto commented Nov 25, 2021 •

edited

rtritto commented Nov 25, 2021 •

edited

timruiterkamp commented Nov 30, 2021

rtritto commented Nov 30, 2021

timruiterkamp commented Nov 30, 2021

rtritto commented Nov 30, 2021 •

edited

timruiterkamp commented Nov 30, 2021

arcanis commented Dec 1, 2021

arcanis commented Dec 1, 2021

kachkaev commented Dec 2, 2021 •

edited

rtritto commented Dec 2, 2021

rtritto commented Dec 2, 2021 •

edited

rtritto commented Dec 2, 2021 •

edited

kachkaev commented Dec 2, 2021 •

edited

kachkaev commented Jan 12, 2022

rtritto commented Jan 12, 2022 •

edited

rtritto commented Jan 13, 2022

balazsorban44 commented Feb 14, 2022

Error: Failed to read source code from amp-dev.js #31812

Error: Failed to read source code from amp-dev.js #31812

Comments

rtritto commented Nov 25, 2021 • edited

What version of Next.js are you using?

What version of Node.js are you using?

What browser are you using?

What operating system are you using?

How are you deploying your application?

Describe the Bug

Expected Behavior

To Reproduce

rtritto commented Nov 25, 2021 • edited

timruiterkamp commented Nov 30, 2021

rtritto commented Nov 30, 2021

timruiterkamp commented Nov 30, 2021

rtritto commented Nov 30, 2021 • edited

timruiterkamp commented Nov 30, 2021

arcanis commented Dec 1, 2021

arcanis commented Dec 1, 2021

kachkaev commented Dec 2, 2021 • edited

rtritto commented Dec 2, 2021

rtritto commented Dec 2, 2021 • edited

rtritto commented Dec 2, 2021 • edited

kachkaev commented Dec 2, 2021 • edited

kachkaev commented Jan 12, 2022

rtritto commented Jan 12, 2022 • edited

rtritto commented Jan 13, 2022

balazsorban44 commented Feb 14, 2022

Error: Failed to read source code from `amp-dev.js` #31812

Error: Failed to read source code from `amp-dev.js` #31812

rtritto commented Nov 25, 2021 •

edited

rtritto commented Nov 25, 2021 •

edited

rtritto commented Nov 30, 2021 •

edited

kachkaev commented Dec 2, 2021 •

edited

rtritto commented Dec 2, 2021 •

edited

rtritto commented Dec 2, 2021 •

edited

kachkaev commented Dec 2, 2021 •

edited

rtritto commented Jan 12, 2022 •

edited