The CLI commands require the Vercel CLI to be installed. You can still use this extension without it, however generally, this CLI creates the .vercel/project.json required for this extension to detect the current project.
Without the Vercel CLI installed globally (install with npm i -g vercel) the following commands will not work:
Run a development server through Vercel
Link current workspace to a Vercel project
Deploy working directory to Vercel
Manage deployments in the activity panel
Add, edit, and remove environment variables without ever leaving VSCode!
This extension will automatically detect any project with a .vercel/project.json file in it and use the project id defined in that file. If you are unsure of where that file comes from, check out the Vercel CLI.
If you already have the Vercel CLI installed, run vercel link in your terminal or use the button on the side panel to connect to a Vercel project.
Select a scope. (Note: This extension will only work with scopes for which permission is granted. Attempting to use it on a disallowed scope will likely return many errors. To avoid this, selecting full account is recommended, but not required)
Select an expiration date. Selecting no expiration will result in the least maintenance, however, selecting a date simply means you will have to generate a new token after that date to continue using this extension
Press Create Token
Copy the code! This is very important, because if you close it without copying, you have to regenerate a new token.
Open VSCode and navigate to settings
If using settings.json, add "vercel.AccessToken": "<YOUR-TOKEN-GOES-HERE>",
if using the settings UI, search for @ext:aarondill.vercel-project-manager-vscode and input your token under Vercel: Access Token
You may have to reload VSCode for the changes to take effect
This extension contributes the following settings: