Vercel provides the following features to customize your deployments:
When your project's code is using private
npm modules that require authentication, you need to perform an additional step to install private modules.
To install private
npm modules, define
NPM_TOKEN as an Environment Variable in your project. Alternatively, define
NPM_RC as an Environment Variable in the contents of the project's npmrc config file that resides at the root of the project folder and is named
~/.npmrc. This file defines the config settings of
npm at the level of the project.
To learn more, check out the guide here if you need help configuring private dependencies.
Vercel ignores certain files and folders by default and prevents them from being uploaded during the deployment process for security and performance reasons. Please note that these ignored files are only relevant when using Vercel CLI.
.hg .git .gitmodules .svn .cache .next .now .vercel .npmignore .dockerignore .gitignore .*.swp .DS_Store .wafpicke-* .lock-wscript .env.local .env.*.local .venv npm-debug.log config.gypi node_modules __pycache__ venv CVS
.vercelignorefile because it is done automatically by Vercel.
Vercel allows you to access the source code and build logs for your deployment using special pathnames for Logs and Source Protection.
All deployment URLs have two special pathnames to access the source code and the build logs:
By default, these routes are protected so that they can only be accessed by you and the members of your Vercel Team.
/_logs to a Deployment URL or Custom Domain in your web browser, you will be able to see a real-time stream of logs from your deployment build processes by clicking on the Building accordion and Serverless Function invocations by clicking on the Functions tab.
/_logs redirect to
https://vercel.com and require logging into your Vercel account to access any sensitive information. By default, a third-party can never access your source or logs by crafting a deployment URL with one of these paths.
You can configure these paths to make them publicly accessible under the Security tab on the Project Settings page. You can learn more about making paths publicly accessible in the Logs and Source Protection section.
On Vercel, you can deploy Git submodules with a Git provider as long as the submodule is publicly accessible via the HTTP protocol. Git submodules that are private or requested over SSH will fail during the Build step.