Where to access the Vega SDK Manager
You can install the Vega SDK Manager from:-
Vega Studio extension:
From the Vega Studio panel, SDK Manager section, select Install SDK Manager.
OR
From the command palette, enter Vega: Install SDK Manager.
See Set Up Vega Studio for more information.
- Vega command-line interface (CLI): Follow the instructions on this page.
Prerequisites
Verify you have the Vega CLI before proceeding. If you have the latest Vega SDK (version 0.22+): You already have the Vega CLI. Proceed to Install the SDK from the CLI. If you have an older Vega SDK version: Upgrade to the latest version by following the Vega SDK installation instructions.Install the SDK from the CLI
-
Run this command to check if you have the Vega CLI:
-
Install the Vega SDK (if needed):
To install the latest SDK version
To install a specific versionTo see available versions
-
Verify your installation:
Create a project
- Install the SDK from the CLI if you haven’t already.
-
Create a
vega-sdk-requirements.jsonfile in your project root: -
Run a health check to verify your environment:
This verifies your SDK installation, checks environment configuration, and identifies potential issues.
How requirements files work
When you run any Vega command in a directory containingvega-sdk-requirements.json, Vega:
- Reads the
vegaSdkVersionfield in the file. - Uses the
vegaSdkVersionfor all SDK operations in that project. - Overrides any global default version settings.
Manage multiple projects
Each project can have its own SDK version by usingvega-sdk-requirements.json:
Update SDK version
Update your SDK to get the latest features and bug fixes.Quick update
-
Check available versions:
-
Install new version:
-
(Optional) Set the new version as your default:
-
(Optional) Clean up old versions:
Safe update (test before committing)
Test new SDK versions in a separate branch before merging:Link existing SDK installation
If you have a Vega SDK installed using the CLI installer or Vega Studio extension, you can link it instead of reinstalling. This saves time and disk space by reusing your existing installation.CI/CD integration
For automated environments like CI/CD pipelines, Vega provides two methods to enable non-interactive mode. This prevents prompts or interactive behavior that would block automation.Non-interactive mode for automation
Method 1: CLI flag (recommended for individual commands) Use the--non-interactive flag to prevent prompts on specific commands.
NONINTERACTIVE environment variable when your entire pipeline should run without any user interaction. This is the preferred approach for CI/CD environments.
Precedence rules
When you use both methods, the CLI flag takes precedence:- CLI flag (
--non-interactive) - Highest priority. - Environment variable (
NONINTERACTIVE=true) - Lower priority. - Default behavior (interactive mode) - Applies when you set neither option.
Advanced features
These advanced configuration options provide additional flexibility for specialized development environments and workflows.Custom configuration file location
By default, Vega stores its configuration in~/vega/config.json. You can customize this location using the VEGA_CONFIG_FILE environment variable. This is useful for:
- Running multiple Vega configurations on the same machine
- Using a shared configuration file across a team
- CI/CD environments where the default path isn’t suitable
- Testing different configurations without affecting your main setup
