EnableSkript
Warns when required VS Code extensions are not enabled in your workspace.
Unlike a simple installed-check, this detects extensions that are installed but
disabled too, because it uses VS Code's extension API to verify each one is
actually active.
Features
- Checks a configurable list of required extension IDs when the workspace opens.
- Shows a warning with a Show Extensions button listing what's missing.
- Re-checks automatically when settings change.
- Re-checks when the active editor switches to a different root in a multi-root
workspace, so per-folder
requiredExtensions are respected.
- Command: EnableSkript: Check Required Extensions (runs on demand and always
reports, even when the warning is disabled).
Settings
All settings have resource scope, so they can be configured per workspace or
folder (.vscode/settings.json).
| Setting |
Type |
Default |
Description |
enableSkript.enableWarning |
boolean |
true |
Enable/disable the warning. |
enableSkript.requiredExtensions |
string[] |
[] |
Extension IDs to require. |
Example workspace configuration
// .vscode/settings.json
{
"enableSkript.enableWarning": true,
"enableSkript.requiredExtensions": [
"esbenp.prettier-vscode",
"ms-vscode.powershell"
]
}
Development
npm install
npm run compile
Press F5 to launch an Extension Development Host for testing.
To exercise the multi-root behavior, pick the Run Extension (multi-root test)
launch configuration. It opens test-fixtures/multi-root.code-workspace, which
has two folders with different requiredExtensions. Switching the active editor
between files in the two roots re-runs the check using each folder's settings.
