Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/ryansuhartanto/turbo-issues/tree/devEngines

Which canary version will you have in your reproduction?

turbo 2.5.7-canary.0

Environment information

CLI:
   Version: 2.5.7-canary.0
   Path to executable: /home/nexus/Dokumen/suhartanto/VCS/turbo-issues/node_modules/.pnpm/turbo-linux-64@2.5.7-canary.0/node_modules/turbo-linux-64/bin/turbo
   Daemon status: Running
   Package manager: pnpm

Platform:
   Architecture: x86_64
   Operating system: linux
   WSL: false
   Available memory (MB): 6187
   Available CPU cores: 8

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Terminal program (TERM_PROGRAM): vscode
   Terminal program version (TERM_PROGRAM_VERSION): 1.104.0
   Shell (SHELL): /usr/bin/fish
   stdin: false

Expected behavior

Turbopack should read the devEngines.packageManager.{name,version}.

Actual behavior

turbo outputs with:

  × Missing `packageManager` field in package.json

To Reproduce

1. Clone repository
2. Switch to devEngines branch
3. Run turbo run build
4. See behavior

Additional context

Information about devEngines:

• The spec: Define spec for development environment field openjs-foundation/package-metadata-interoperability-collab-space#15
• Corepack support: https://github.com/nodejs/corepack?tab=readme-ov-file#devenginespackagemanager

  If the top-level packageManager field is missing, Corepack will use the package manager defined in devEngines.packageManager

• Officially documented in package.json: https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines

  The supported keys under the devEngines property are cpu, os, libc, runtime, and packageManager.

• Quote "it is the new standard" by maintainer of @pnpm: https://github.com/orgs/pnpm/discussions/9817#discussioncomment-13973040