Skip to content

Conversation

@ConsoleTVs
Copy link
Contributor

Description

Forces the package manager to be pnpm by using devEngines option on package.json.

For NPM:

npm error code EBADDEVENGINES
npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
npm error EBADDEVENGINES Invalid engine "packageManager"
npm error EBADDEVENGINES Invalid name "pnpm" does not match "npm" for "packageManager"
npm error EBADDEVENGINES {
npm error EBADDEVENGINES   current: { name: 'npm', version: '11.3.0' },
npm error EBADDEVENGINES   required: { name: 'pnpm', onFail: 'error' }
npm error EBADDEVENGINES }

For Yarn:

This project is configured to use pnpm because package.json has a "packageManager" field

For pnpm:

Scope: all 238 workspace projects
Packages: +88
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 1359, reused 1197, downloaded 0, added 88, done

@sapphi-red sapphi-red changed the title fix: only allow pnpm using devEngines chore: only allow pnpm using devEngines Jun 14, 2025
@sapphi-red sapphi-red added the p1-chore Doesn't change code behavior (priority) label Jun 14, 2025
@ConsoleTVs
Copy link
Contributor Author

I think this is a relatively safe merge. Is there anything blocking to be aware of?

@bluwy bluwy merged commit a7196d9 into vitejs:main Nov 27, 2025
16 checks passed
@bluwy
Copy link
Member

bluwy commented Nov 27, 2025

I wanted another review in case I forgot something, but I'm merging this now since it's been a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

p1-chore Doesn't change code behavior (priority)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants