Skip to content

Add optimized extensions.json for VSCode recommendations #30974

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
saiganesh47 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add optimized extensions.json for VSCode recommendations #30974

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .vscode/optimized extensions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
{
"recommendations": [
"rust-lang.rust-analyzer",

"clang.clangd",
"ms-vscode.cmake-tools",
"xaver.clang-format",
"vadimcn.vscode-lldb",

"oven.bun-vscode",
"esbenp.prettier-vscode",

"better-ts-errors.better-ts-errors",
"MylesMurphy.prettify-ts",

"bierner.markdown-preview-github-styles",
"bierner.markdown-emoji",
"bierner.emojisense",
"bierner.markdown-checkbox",
"bierner.jsdoc-markdown-highlighting",

"tamasfe.even-better-toml",

"bierner.comment-tagged-templates"
]
}
Comment on lines +1 to +26
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

What exact workspace file path does VS Code use for extension recommendations, and does it auto-read files other than .vscode/extensions.json?

💡 Result:

Visual Studio Code uses the.vscode/extensions.json file located at the root of your workspace folder to define workspace-specific extension recommendations [1][2][3]. Regarding your questions: 1. Exact File Path: For a single-folder workspace, the file is located at.vscode/extensions.json [1][3]. In a multi-root workspace, recommendations can be defined within the.code-workspace file itself under the extensions.recommendations property, or you can continue to use individual.vscode/extensions.json files within each folder of the multi-root workspace [1][3]. 2. Auto-reading other files: VS Code does not automatically read files other than.vscode/extensions.json (or the.code-workspace file) to populate the official "Workspace Recommendations" list [1][2]. While VS Code may suggest extensions based on other factors—such as "Other Recommendations" based on recently opened files or the programming languages detected in your workspace—these are managed by the editor's internal heuristics rather than by reading arbitrary user-defined JSON files [1]. If you need to manage recommendations, you should use the built-in command "Extensions: Configure Recommended Extensions (Workspace Folder)" to ensure the configuration is placed in the correct, recognized location [1][3].

Citations:

🏁 Script executed:

#!/bin/bash
# Search for references to "optimized extensions" or custom extension loading
echo "=== Searching for references to 'optimized extensions' ==="
rg -i "optimized.extensions" --type json --type js --type ts --type py --type sh

echo "=== Searching for any custom extension recommendation handling ==="
rg -i "extensions\.json|extension.*recommendation" --type json --type js --type ts --type py --type sh -B 2 -A 2

echo "=== Listing .vscode directory contents ==="
find .vscode -type f 2>/dev/null | head -20

Repository: oven-sh/bun

Length of output: 373

🏁 Script executed:

#!/bin/bash
echo "=== Content of .vscode/extensions.json ==="
cat .vscode/extensions.json

echo -e "\n=== Content of .vscode/optimized extensions.json ==="
cat ".vscode/optimized extensions.json"

echo -e "\n=== Comparison ==="
if diff -q .vscode/extensions.json ".vscode/optimized extensions.json" >/dev/null 2>&1; then
  echo "Files are identical"
else
  echo "Files differ"
  diff .vscode/extensions.json ".vscode/optimized extensions.json"
fi

Repository: oven-sh/bun

Length of output: 1636

Remove or consolidate with .vscode/extensions.json.

VS Code only auto-reads .vscode/extensions.json for workspace extension recommendations—custom filenames like .vscode/optimized extensions.json are ignored. The repository already has .vscode/extensions.json (with category comments); this "optimized" version is dead code. Either delete this file or, if the clean version is preferred, update the standard file instead.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.vscode/optimized extensions.json around lines 1 - 26, The file "optimized
extensions.json" duplicates workspace recommendations and is ignored by VS Code;
either delete "optimized extensions.json" or merge its "recommendations" array
into the existing "extensions.json" (consolidate and dedupe entries such as
"rust-lang.rust-analyzer", "esbenp.prettier-vscode", etc.), preserve any desired
comments/ordering from the current canonical "extensions.json", and remove the
orphaned "optimized extensions.json" to avoid stale/dead configuration.