Overview
Design Tokens Explorer supports loading any number of token sources in parallel. Each source appears as a separate panel in the sidebar, switchable via a dropdown. This is useful when your design system is split across multiple packages, themes, or token categories.Basic multi-source setup
settings.json
Common use cases
Design system packages
When consuming a published design system alongside local overrides:settings.json
Theming (light / dark)
When you maintain separate token files for themes:settings.json
Remote + local
Combining tokens from a remote design tool export with local additions:settings.json
Monorepo
In a monorepo with tokens in multiple packages:settings.json
Sharing settings across a team
Token source configuration is typically kept in workspace settings (.vscode/settings.json) so it is shared with the team:
.vscode/settings.json
Reload behavior
- Local sources are watched for file changes. When any source file is saved, only that source is reloaded — other sources remain cached.
- Remote sources are fetched once on activation. To re-fetch, run Design Tokens: Refresh Sources.
- When any source changes (file or config), the adoption audit re-runs in the background automatically.