Rank, 14 days: 20 on the Next.js sheet
1 person reported

All time, since Oct 6.

Config imports resolve against cwd

“When the working directory is not the project directory, relative imports in next.config.ts are resolved against process.cwd().”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4116/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Relative imports in next.config.ts resolve against cwd, not config directory. Building or running dev from outside the project directory fails with a missing module, or silently loads a same-path file under the cwd.

Is this your bug?

File my report
Where
next.config.ts loading
Error text
Error: Cannot find module './src/headers'
Versions
15.5.28 to 16.4.0-canary.63
Platforms
Linux, macOS
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. next.config.ts: backport #99743 to 15.5.x — relative imports resolve against process.cwd()On GitHub#100978
  2. next.config.ts: relative imports resolve against process.cwd() instead of the config file's directoryOn GitHub#99742

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.