-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop -- in pnpm invocation for pnpm 7+ #1432
Conversation
Deployment failed with the following error:
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super annoying that we even have to do this, but good for now.
This is the upstream change: pnpm/pnpm#4290 |
pnpm
handling of--
changed for v7.This is not the ideal way to implement this check, but our current abstraction of backends doesn't really allow for anything stateful (e.g. version). Rather than make a new backend for pre- and post-
pnpm@7
, I added a check for the version that runs once perturbo run
whenpnpm
is being used.A better implementation might in the future include a stateful version field in the backend and the ability to check semver constraints.