如何通过终端启用VSCode扩展？现有CLI无对应操作求解

Great question! I've looked into this myself, and you're spot on—there's no official --enable-extension CLI flag in VS Code's documented command-line options, only the set you listed:

• --install-extension
• --uninstall-extension
• --disable-extensions (disables all extensions globally)
• --list-extensions
• --show-versions
• --enable-proposed-api

That said, there's a reliable workaround by modifying VS Code's user settings file, where extension enable/disable states are stored. Here's how to automate this:

Step 1: Grab the Extension ID #

First, confirm the full unique ID of the extension you want to enable using:

code --list-extensions

This will output IDs like ms-python.python or dbaeumer.vscode-eslint—copy the one you need.

Step 2: Edit the Settings File Programmatically #

VS Code stores extension states in settings.json, with paths varying by OS:

• Linux: ~/.config/Code/User/settings.json
• macOS: ~/Library/Application Support/Code/User/settings.json
• Windows: %APPDATA%\Code\User\settings.json

For Linux/macOS (using jq for JSON editing) #

If the extension was previously disabled, it’ll be in the extensions.disabledExtensions array. Run this command to remove it from the disabled list (which enables it):

# Replace YOUR_EXTENSION_ID with the actual ID from Step 1
jq '.extensions.disabledExtensions |= map(select(. != "YOUR_EXTENSION_ID"))' ~/.config/Code/User/settings.json > temp.json && mv temp.json ~/.config/Code/User/settings.json

For Windows (PowerShell) #

Use PowerShell to modify the JSON file without manual editing:

# Replace YOUR_EXTENSION_ID with the actual ID from Step 1
$settingsPath = "$env:APPDATA\Code\User\settings.json"
$settings = Get-Content $settingsPath | ConvertFrom-Json
$settings.extensions.disabledExtensions = $settings.extensions.disabledExtensions | Where-Object { $_ -ne "YOUR_EXTENSION_ID" }
$settings | ConvertTo-Json -Depth 10 | Set-Content $settingsPath

Quick Note for Default-Enabled Extensions #

If the extension was installed but never explicitly disabled, it should already be enabled by default. If it’s not working, double-check that it’s not hidden in the disabled list, or reinstall it with code --install-extension YOUR_EXTENSION_ID to reset its state.

Why No Official Flag? #

From community discussions, the VS Code team hasn’t prioritized adding an --enable-extension flag because the enable/disable state is tightly tied to user settings, and modifying those via CLI covers the core use case. There are open feature requests for this, though, so it might be added in a future release.

内容的提问来源于stack exchange，提问作者suchcodemuchwow