Support devEngines in package.json

[Jiralite]

Goals

1. Support devEngines in package.json

Background

The devEngines field in the package.json should be supported. Currently, only packageManager is scanned:

turborepo/crates/turborepo-repository/src/package_manager/mod.rs

Lines 455 to 458 in 13bfef4

	fn read_package_manager(pkg: &PackageJson) -> Result<Self, Error> {
	let Some(package_manager) = &pkg.package_manager else {
	return Err(Error::MissingPackageManager);
	};

I noticed pnpm is used here. pnpm also does not support devEngines as of now: pnpm/pnpm#8153

Proposal

During this period, I believe both should be checked with a priority of devEngines.

[anthonyshew]

We are definitely excited to upgrade from packageManager to devEngines along with the rest of the ecosystem.

Has devEngines been officially accepted/implemented into Node.js? I see the pnpm issue you've linked. What about npm and yarn?

We will need to come up with a sensible migration strategy to handle the matrix of packageManager || devEngines && package manager && turbo but I don't believe we will have a problem doing so.

[Jiralite]

npm supports this (npm/cli#7766). For the others, I found these which are great to read for context:

• Implement devEngines proposal from Package Metadata Interoperability Collab Space nodejs/corepack#567
• deps: remove corepack nodejs/node#51981 (Definitely check this out. A Node.js member opened this)
• Wishlist on managing package manager versions in a Node.js application nodejs/package-maintenance#609
• feat: add proposal for binary management nodejs/package-maintenance#594
• [Feature] Alternative to Node.js experimental corepack to manage package manager version  yarnpkg/berry#6443

So ultimately, it seems adoption is still in progress with Node.js seemingly planning to remove corepack in favour of devEngines.

[anthonyshew]

Great, thank you for finding those. We'll be looking to this when we can.