The Imports Setting
Thevscode_vibrancy.imports setting accepts an array of file paths to CSS and JavaScript files.
Key Points
- Files are imported in the order they appear in the array
- Files ending in
.cssare loaded as stylesheets - Files ending in
.jsare loaded as scripts - Paths must be absolute (not relative)
- On Windows, use forward slashes (
/) instead of backslashes - Changes require running “Reload Vibrancy” (F1) and restarting VS Code
Path Examples
- macOS
- Windows
- Linux
Creating a Custom CSS Theme
Step 1: Create Your CSS File
Create a new CSS file in a location of your choice:Step 2: Configure Imports
Add the file path to your settings:Set the theme to
"Custom theme (use imports)" to use only your custom files without any default Vibrancy theme.Step 3: Apply Changes
- Save your settings
- Press F1 and run “Reload Vibrancy”
- Restart VS Code when prompted
Example Custom Themes
Minimal Transparency Theme
High Contrast Transparent Theme
Gradient Background Theme
Custom Color Accents
Using JavaScript
You can also inject custom JavaScript to add dynamic behavior:Modifying Existing Themes
You can use imports to tweak existing Vibrancy themes:Inspecting VS Code Elements
To find CSS selectors for customization:-
Open VS Code Developer Tools:
- Press
Cmd/Ctrl + Shift + P - Run “Developer: Toggle Developer Tools”
- Press
- Use the element inspector (click the arrow icon)
- Click on the UI element you want to customize
- Note the CSS classes and structure in the Elements panel
- Use those selectors in your custom CSS
VS Code uses the Monaco editor’s CSS classes extensively. Look for classes starting with
.monaco- for editor-related elements.Common CSS Selectors
Here are some useful CSS selectors for customizing VS Code:Example: Complete Custom Theme
Here’s a complete example of a custom theme: custom-purple-theme.css:Referencing Existing Themes
You can study the built-in Vibrancy themes for inspiration:- Find your VS Code installation directory
- Navigate to the extension directory:
- macOS:
~/.vscode/extensions/illixion.vscode-vibrancy-continued-*/themes/ - Windows:
%USERPROFILE%\.vscode\extensions\illixion.vscode-vibrancy-continued-*\themes\
- macOS:
- Open any
.cssfile to see how themes are structured
Troubleshooting
Custom CSS not loading
Custom CSS not loading
Possible causes:
- File path is incorrect
- File doesn’t exist at specified location
- Wrong path separator on Windows (use
/not\) - Vibrancy hasn’t been reloaded
- Verify the file exists at the exact path specified
- Check for typos in the path
- Run “Reload Vibrancy” (F1)
- Restart VS Code
- Check the Console in Developer Tools for error messages
Custom styles not applying
Custom styles not applying
Possible causes:
- CSS specificity too low
- VS Code’s styles are overriding yours
- Styles cached from previous reload
- Add
!importantto your CSS rules - Increase selector specificity
- Clear VS Code cache and reload
- Check Developer Tools to see if styles are being applied
Import error notification
Import error notification
If you see: “Couldn’t open custom import file”Solutions:
- Verify file path is absolute (not relative)
- Check file permissions (must be readable)
- Remove placeholder
/path/to/filefrom imports array - Ensure file extension is
.cssor.js
JavaScript not executing
JavaScript not executing
Possible causes:
- File path is incorrect
- JavaScript errors in your code
- Content Security Policy blocking execution
- Check Developer Tools Console for errors
- Verify file path and extension (
.js) - Test with simple script first (e.g.,
console.log('test')) - Wrap code in try-catch blocks
Best Practices
Organization
- Keep all custom theme files in one directory
- Use descriptive filenames (e.g.,
vibrancy-purple-accent.css) - Comment your CSS for future reference
- Version control your custom themes with git
Performance
- Minimize the number of imported files
- Avoid heavy JavaScript operations
- Use CSS variables for easier maintenance
- Test performance with Developer Tools
Maintenance
- Keep backups of working themes
- Document color values and design decisions
- Test themes after VS Code updates
- Share your themes with the community
Sharing Your Theme
If you create a great custom theme:- Share the CSS file on GitHub
- Create a pull request to add it to the official themes directory
- Share in the Vibrancy Discussions
- Write a blog post or tutorial

