Add --cwd argument to vercel pull command #1#55
Open
MangoPieface wants to merge 2 commits intovercel:mainfrom
Open
Add --cwd argument to vercel pull command #1#55MangoPieface wants to merge 2 commits intovercel:mainfrom
MangoPieface wants to merge 2 commits intovercel:mainfrom
Conversation
…tom_working_directory_1 Add --cwd argument to vercel pull command
MangoPieface
requested review from
TooTallNate,
jeffsee55 and
paulogdm
as code owners
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.
Problem
When using
vercel pullto deploy a project in a subdirector the vercel pull command runs without the--cwdargument, while vercel deploy correctly includes it.This causes vercel pull to create the .
vercel/folder in the repository root, butvercel deploy --cwd=<path>looks for it in the subdirectory. Since the.vercel/project.jsonisn't found, Vercel cannot detect the framework configuration.This results in "No framework detected" in deployment logs and Only static assets being deployed instead of the full application (serverless functions, SSR pages, etc.)
Fix
Add the --cwd argument to vercelPullArgs when vercelCurrentWorkingDirectory.
Testing
I have not tested this (apologies), but we've included this in our workaround in a pipeline.