Dev server exits early in Next15 when using Turbopack

[samcx]

Discussed in #73025

^{Originally posted by MangoMarcus November 20, 2024}

Link to the code that reproduces this issue

https://github.com/MangoMarcus/turbopack-exit

To Reproduce

• Install with npm i
• Run development server with npm run dev
• Open http://localhost:3000 in your browser
• npm run dev will exit with code 0, without an error.

Current vs. Expected behavior

npm run dev will exit with code 0, without an error

Provide environment information

Operating System:
  Platform: macOS
  Chip: Apple M1 Pro
  Version: macOS 14.4
Binaries:
  Node: 20.2.0
  npm: 9.6.6
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.3
  eslint-config-next: 15.0.3
  react: [email protected]
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.6.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

This was not an issue before migrating to Next 15 and also only affects Turbopack, not Webpack. I've narrowed down the issue to Preline, although I'm not sure if the underlying issue is with Next, Turbopack, or Preline. As it works fine on either Next 14 or Webpack, I'm guessing it's not Preline itself that's the issue.

I've added some 'XXX' comments for context, it seems the process exits whenever a Preline import is read, eg. console.log(typeof Preline)