question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Causes an error when any folder in the path starts with "ud"

See original GitHub issue

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

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:2
  • Comments:13 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
jonrynncommented, May 3, 2022

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

2reactions
dewald-elscommented, Jul 9, 2022

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

A file copy operation fails when files or folders have long paths ...
The files or folders that you copy have paths that exceed the maximum allowable path length. In this scenario, the behavior of the...
Read more >
11 Ways to Fix "The System Cannot Find The Path Specified ...
1. Run Command Prompt as an Administrator ... Windows utilities cannot access all files and folders available on your device. Administrative ...
Read more >
"Could not find a part of the path" error message
Account through which your application is running don't have rights to create directory at path location, like if you are trying to create ......
Read more >
Best Practice: Working with Paths in Python - Part 1 - b.telligent
The variables assigned upon execution immediately cause an error: ... files and folders. os.path.isdir checks for us whether there is a folder below...
Read more >
Troubleshooting AWS CLI errors - AWS Command Line Interface
If you receive an error that indicates that a command doesn't exist, ... Possible cause: The operating system PATH was not updated during...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found