-
Notifications
You must be signed in to change notification settings - Fork 517
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
docs(deploy): flag and setting for legacy #635
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I don't know why CI fails |
docs/cli/deploy.md
Outdated
## --legacy | ||
|
||
Force legacy deploy implementation. | ||
|
||
Since pnpm v10, by default, `pnpm deploy` will try creating a dedicated lockfile from a shared lockfile for deployment. The `--legacy` flag disables this behavior. | ||
|
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.
also mention the injected dependencies setting that is required in v10
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.
c817778 has added mention of this setting.
I added it to near top instead of --legacy
because this setting is required by both legacy and the new implementation.
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.
I don't understand. Isn't legacy the algorithm from pnpm v9, which didn't require injected deps?
No description provided.