Turbopack Error: "Next.js package not found" during pnpm dev

[mjeanbosco19]

Link to the code that reproduces this issue

https://github.com/mjeanbosco19/events-mis

To Reproduce

To Reproduce

1. Clone the Repository: https://github.com/mjeanbosco19/events-mis
2. Use pnpm to install all project dependencies
3. Run the development server using Turbopack: pnpm dev
4. Observe the Error

Current vs. Expected behavior

Current Behavior when running the development server with pnpm dev, the process fails, and the following error message is displayed in the terminal:

FATAL: An unexpected Turbopack error occurred.
Error [TurbopackInternalError]: Next.js package not found

Debug info:

• Execution of get_entrypoints_with_issues failed
• Execution of Project::entrypoints failed
• Execution of AppProject::routes failed
• Execution of directory_tree_to_entrypoints_internal failed
• Execution of directory_tree_to_loader_tree failed
• Execution of *FileSystemPath::join failed
• Execution of get_next_package failed
• Next.js package not found
  No additional logs are generated in the provided log file path:
  C:\Users\pc\AppData\Local\Temp\next-panic-4bc82ebe23177e94ca24c26cf186725.log.

This prevents the development server from starting and halts all development work.

Expected Behavior the development server should start successfully using Turbopack when running the pnpm dev command. Expected output in the terminal should look like:

▲ Next.js 15.1.4 (Turbopack)

• Local: http://localhost:3000
• Network: http://192.168.1.81:3000
• Environments: .env

✓ Starting...
The application should be accessible at the specified local and network URLs without errors.

Provide environment information

$ npx --no-install next info
'yarn' is not recognized as an internal or external command,
operable program or batch file.

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 12013
  Available CPU cores: 8
Binaries:
  Node: 22.13.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 9.15.4
Relevant Packages:
  next: 15.2.0-canary.20 // Latest available version is detected (15.2.0-canary.20).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.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

The issue occurs locally while running the development server using pnpm dev. No deployment platform is involved; this error arises during local development.

[niels-bosman]

We were having the same issue after moving from bun.lockb to bun.lock with Bun 1.2. We reverted to a bun.lockb file for now to alleviate the issue.

[RiskyMH]

I think I fixed niels-bosman's issue in #74056, there just hasn't been a full stable release yet.

My solution was to just add empty bun.lockb file lol