V15.5.26

Name: V15.5.26 bug reports
Creator: AI & Agent Dev Bug Sandbox

Reports that share this version, grouped in one feed.

Similar Reports

high68%

Turbopack: "type": "commonjs" in package.json breaks every App Router source file

Setting `"type": "commonjs"` in a Next.js project using Turbopack causes build and dev failures because Turbopack enforces the declared module format on App Router source files (which are written as ESM) and on generated `.next-internal` server-action entries, even though Webpack ignores this field. The issue affects all App Router files and internal virtual modules, not just the `'use client'` proxy previously fixed.

V15.5.26 V16.3.5 V16.3.6 V16.4.0-Canary.43 Next.js

high95%

next.config.ts relative imports resolve against process.cwd() instead of config file directory

When Next.js is invoked from a directory other than the project root, relative imports in next.config.ts are resolved against the current working directory instead of the configuration file's own directory, leading to module resolution failures or loading incorrect files.

V15.0.0 V15.5.26 V16.4.0-Canary.63 Next.js

high95%

next.config.ts relative imports resolve against process.cwd() instead of the config file's directory

When Next.js is invoked from a directory other than the project root (e.g., `node app/node_modules/next/dist/bin/next build app`), relative imports in `next.config.ts` are resolved against `process.cwd()` instead of the config file's directory. This causes builds to fail with `Cannot find module` or silently load a wrong file if a similarly named file exists in the cwd. The issue affects the default SWC transpilation path and has been present since Next.js 15.0.0.

V15.0.0 V15.5.26 V16.4.0-Canary.63 Next.js

high95%

Relative imports in next.config.ts resolve against process.cwd() instead of the config file directory

When building a Next.js project with next.config.ts from a working directory different from the project root, relative imports inside next.config.ts are resolved relative to process.cwd() rather than the config file's location. This causes module-not-found errors or, worse, silently loads a file with the same relative path from the current working directory, potentially applying unintended configuration.

V15.0.0 V15.5.26 V16.4.0-Canary.63 Next.js