[email protected] turbopack incompatible with typeorm? The "paths[0]" argument must be of type string. Received undefined

[simon300000]

Summary

I was gonna write an issue, but I am not sure if this is actually cause by next.js or typeorm.

It seems like, turbopack will cause The "paths[0]" argument must be of type string. Received undefined, when typeorm is involved in server actions.

I have a reproduce repository: https://github.com/simon300000/turbopack-reproduce

To reproduce:

1. npm install
2. start the application in development npm run dev
3. open http://localhost:3000

npm run dev without turbopack works fine.
build is not affected.

Also exist on next@latest, but reproduce template gave me canary.

I can reproduce this issue with GitHub codespace as well

Affected Version

I tested different next versions, it seems like this issue first appeared on 5.2.0, 5.1.7 was not affected.

For canary version, [email protected] wan affected, [email protected] was not.
There might be one commit from v15.2.0-canary.39...v15.2.0-canary.40
that caused this?

Additional information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.3.0: Thu Jan  2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 23.1.0
  npm: 10.9.0
  Yarn: 1.22.15
  pnpm: 6.11.0
Relevant Packages:
  next: 15.2.2-canary.2 // Latest available version is detected (15.2.2-canary.2).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.8.2
Next.js Config:
  output: N/A

Example

https://github.com/simon300000/turbopack-reproduce

Error in console

⨯ TypeError: The "paths[0]" argument must be of type string. Received undefined
at [project]/node_modules/typeorm/globals.js [app-rsc] (ecmascript) (file:/workspaces/turbopack-reproduce/src/globals.ts:4:0)
at [project]/node_modules/typeorm/index.js [app-rsc] (ecmascript) (file:/workspaces/turbopack-reproduce/src/index.ts:9:0)
at [project]/app/a.ts [app-rsc] (ecmascript) (app/a.ts:2:0)
at [project]/.next-internal/server/app/page/actions.js { ACTIONS_MODULE0 => "[project]/app/a.ts [app-rsc] (ecmascript)" } [app-rsc] (server actions loader, ecmascript) (.next/server/chunks/ssr/[root of the server]__21588afe..js:178:134)
at [project]/.next-internal/server/app/page/actions.js { ACTIONS_MODULE0 => "[project]/app/a.ts [app-rsc] (ecmascript)" } [app-rsc] (server actions loader, ecmascript) (.next/server/chunks/ssr/[root of the server]__21588afe..js:200:351)
at Object. (.next/server/app/page.js:22:9)
2 | import { PlatformTools } from "./platform/PlatformTools"
3 | import { DataSourceOptions } from "./data-source/DataSourceOptions"

4 | import { ConnectionOptionsReader } from "./connection/ConnectionOptionsReader"
5 | import { ConnectionManager } from "./connection/ConnectionManager"
6 | import { getFromContainer } from "./container"
7 | import { DataSource } from "./data-source/DataSource" {
code: 'ERR_INVALID_ARG_TYPE',
page: '/'
}

[nguyennamduong]

I got same issue recently. Added this to next.config.ts and it works.

const nextConfig: NextConfig = { serverExternalPackages: ["typeorm"], };

[nivmamedov]

I had faced the issue too, fixed by this comment, mind ellaborating how you'd come to this?