Fix package.json#packageManager to correct pnpm version #2046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dub currently fails to build with
pnpm@8.6.10
. This PR upgradespackage.json#packageManager
to a version that succeeds.Why Vercel builds currently succeed
package.json#packageManager
is ignored on Vercel when corepack is not enabled. Instead, thepnpm-lock.yaml
is detected as a lockfile generated bypnpm@9
, sopnpm@9.15.5
is used.Why
pnpm@8.6.10
builds failThe existing
pnpm-lock.yaml
is version 9. This means it was generated by pnpm 9 or 10, and it can only be read by pnpm 8. pnpm 8 ignores it, upgradestypescript
from5.4.4
->5.6.2
, and the build fails due to a type error:When
package.json#packageManager
matterspackage.json#packageManager
is used when corepack is enabled OR when pnpm 10 is used.