Revert "[cli] move builders to peer dependencies"#15022
Conversation
This reverts commit fa4e1cd.
🦋 Changeset detectedLatest commit: 649cb3f The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-ljghj594a.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-ljghj594a.vercel.sh/tarballs/vercel.tgz"
}
}
} |
🧪 Unit Test StrategyComparing: Strategy: Code changed outside of a package - running all unit tests Affected packages - 15 (38%)
Unaffected packages - 25 (63%)
Results
This comment is automatically generated based on the affected testing strategy |
Merged in #14763, reverted in #15022. Re-submitting and running e2e tests now via label. e2e tests are coming back by default to PRs in #15008 - Moves builders to peerDependencies and tells pnpm that they're optional dependencies. With this config, `pnpm` will not bundle them into the publishd `vercel` CLI, but they will be in the manifest. - Add a feature to the `resolveBuilders` function that reads the peerDependencies section of package.json at runtime and installs that correct version of the builder. It stores this builder in a local cache (`.vercel/builders`) so it only has to get them from the registry once. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Reverts #14763
Note
Low Risk Change
This PR reverts a previous change that moved builders to peer dependencies, restoring them as direct dependencies in package.json and simplifying the builder resolution logic - purely a dependency management and build configuration change with no security implications.
Risk assessment for commit 649cb3f.