If your code is located in a subdirectory, you'll find it useful that connecting one of your Git repositories to Vercel will prompt you for specifying a Root Directory.
Additionally, you can now select a different Framework or overwrite its default settings:
Select the right settings for your needs when importing repositories.
Once you've deployed your project, you might still want to continue tweaking its configuration until it meets all your needs – no matter how advanced they are.
Because of that, you can now fully customize all of the options mentioned above right from the Project Settings:
Adjust your project's configuration at any time.
All of the fields are automatically optimized for your Framework by default. Overwriting one of them, however, is as easy as turning on the
After importing your Git repository, every push and pull request gets deployed automatically. However, sometimes you might want to create a quick manual deployment from the CLI.
To make this easy, creating new projects through our command-line interface now surfaces the automatically detected configuration and lets you edit it on the fly:
Setting up a new Vercel project using Vercel CLI.
For subsequent deployments, those values naturally don't have to be configured:
Deploying to an existing Vercel project using Vercel CLI.
vercel dev,please make sure to first deploy using
vercel --confirmcan be run to auto-confirm the prompts.
Aside from allowing for customizing your Framework settings, as you can see, Vercel CLI now also lets you link your local codebase to any project on Vercel – no matter its name or scope.
Thanks to the above changes, several new use cases are now possible:
- Projects without a
package.jsonfile (like Hugo or Jekyll sites) can be deployed.
- Your project can be located in a subdirectory of your Git repository.
- The Build Command, Development Command, and Output Directory can be customized.
--nameflag is now deprecated in Vercel CLI.