next.js: Causes an error when any folder in the path starts with "ud"

Verify canary release

I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
Binaries:
  Node: 16.13.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 12.1.5-canary.6
  react: 18.0.0
  react-dom: 18.0.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

pnpm run dev

Describe the Bug

As the title says, I found that I could not successfully run the project using pnpm run dev or yarn run dev when any of the folders in the path started with “ud”.

I’ve tested this on two computers (both windows) and I get the same error, here is what I got:

> ud-test@0.1.0 dev D:\Dev\ud-test
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
wait  - compiling...
error - ./node_modules/.pnpm/next@12.1.5-canary.6_react-dom@18.0.0+react@18.0.0/node_modules/next/dist/client/dev/amp-dev.js
Module not found: Can't resolve 'D:\Devud-test\node_modules\.pnpm\next@12.1.5-canary.6_react-dom@18.0.0+react@18.0.0\node_modules\next\dist\compiled\regenerator-runtime\runtime.js' in 'D:\Dev\ud-test\node_modules\.pnpm\next@12.1.5-canary.6_react-dom@18.0.0+react@18.0.0\node_modules\next\dist\client\dev'

Expected Behavior

Dev server normally runs up.

To Reproduce

run pnpm create next-app to create a project name that starts with “ud”.
pnpm run dev or yarn run dev

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 6
Comments: 23 (5 by maintainers)

Commits related to this issue

Move files to out of the dir "udemy" for fixing issue https://github.com/vercel/next.js/issues/36078 — committed to hskwakr/misc-react by hskwakr a year ago

Most upvoted comments

It worked when I didn’t use udemy – seriously, someone wrote next.js so you can’t have udemy in the folder name?

jonrynn on May 3, 2022

I’m having a similar if not the same issue.

After upgrading to 13.4.4 I’m getting the error Error: Filesystem cache is not enabled, cannot read plugin from phsyical path when running npm run build (btw note the typo in phsyical).

When running npm run dev the error looks like this: Error: Cannot find module '/Users/simon.knittel/Documents/hmmh/snivy/app/.next/fallback-build-manifest.json'

As far as I can see, there is no ud in that path or anywhere in my filenames.

This also happens on our Jenkins.

However, in contrast to @TimFL, only 13.4.4 is broken for me. Downgrading to 13.4.3 reverts the issue.

Getting the same issue with swcPlugins: [["next-superjson-plugin", {}]], and next 13.4.4

timheerwagen on May 31, 2023

I’m having a similar if not the same issue.

After upgrading to 13.4.4 I’m getting the error Error: Filesystem cache is not enabled, cannot read plugin from phsyical path when running npm run build (btw note the typo in phsyical).

When running npm run dev the error looks like this: Error: Cannot find module '/Users/simon.knittel/Documents/hmmh/snivy/app/.next/fallback-build-manifest.json'

As far as I can see, there is no ud in that path or anywhere in my filenames.

This also happens on our Jenkins.

However, in contrast to @TimFL, only 13.4.4 is broken for me. Downgrading to 13.4.3 reverts the issue.

simonknittel on May 30, 2023

Is there no work being done on this?

Found this issue being linked here: https://github.com/vercel/next.js/issues/37508 I have the exact same error as issue 37508 with the difference being, that none of my paths contain “ud” anywhere. Is there no workaround for this yet?

Next@13.4.2 is the last release that worked for me, 13.4.3 upwards (up to latest canary 13.4.5-canary0) keep throwing the amp-dev and fallback-build-manifest.json errors in console, completely nuking my project.

Tried the following things:

With and without nodeLinker: node-modules in yarnrc
yarn cache clear & reinstall
Nuke .next folder (multiple times)
swcFileReading: false in experimental settings
Remove all spaces from absolute filepath
Double check all folders for “ud” in them, there are none

TimFL on May 30, 2023

Same issue occurred for me, Had the folder initially named udemy-next-auth, I then changed it to next-auth-section and it worked.

dewald-els on Jul 9, 2022

tracking PR: https://github.com/vercel/next.js/pull/50651

thekip on Jun 1, 2023

oh. my. gosh. this is the error!!! i was going insane 😂👍 for the record, i am a windows user (please don’t shun me).

thank you 🙏🖤

andreagodoshian on Aug 8, 2022

@balazsorban44 I tried several releases and the oldest I tried https://github.com/vercel/next.js/releases/tag/v12.0.8-canary.10

the issue also occurred

ryanadhi on Jun 23, 2022

Anyone who can reproduce this issue and say that it worked in previous versions, could you bisect and find the exact canary release? That would help us pinpoint the PR that introduced the issue. You can see the full list of releases here: https://github.com/vercel/next.js/releases

balazsorban44 on Jun 14, 2022