Fix Vercel build: convert repo to pnpm workspace#2
Open
SomethingNew71 wants to merge 1 commit into
Open
Conversation
Vercel runs `pnpm install` at the repo root, which previously only installed `concurrently` (the sole root devDependency). The build script then `cd frontend && pnpm build`'d into a project with no node_modules, failing with `nuxt: command not found`. Adding a pnpm-workspace.yaml that includes `frontend` makes the root install pull in the frontend's deps, so the existing build script works on Vercel without changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
nuxt: command not foundbecausepnpm installat the repo root only installed the root's lone devDependency (concurrently). The build script then didcd frontend && pnpm buildagainst a project that had nonode_modules.pnpm-workspace.yamllistingfrontend. Now a single rootpnpm installresolves and installs the frontend's dependencies too, so the existingpnpm buildworks on Vercel without touching Vercel settings..andfrontend).Sidecar (Python) is intentionally not part of the workspace — it has no
package.jsonand isn't deployed to Vercel.Test plan
pnpm installat repo root pulls frontend depspnpm run buildproducesfrontend/.outputsuccessfully