Add optimized extensions.json for VSCode recommendations

[saiganesh47]

What does this PR do?

How did you verify your code works?

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[coderabbitai]

Walkthrough

This PR adds a .vscode/optimized extensions.json configuration file to the Bun repository that recommends a curated set of VS Code extensions for developers. The file defines a recommendations array with fourteen extensions covering Rust development, C/C++ tooling, code formatting, debugging, and documentation helpers.

Changes

VS Code Recommended Extensions

Layer / File(s)	Summary
VS Code extensions configuration .vscode/optimized extensions.json	Introduces a VS Code workspace recommendations file listing fourteen extensions: Rust analyzer, C/C++ tools, clang-format, LLDB debugger, Bun plugin, Prettier, TypeScript error tooling, Markdown GitHub styling and emoji support, TOML syntax highlighting, and comment-tagged-template formatting.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description contains only template placeholders with no actual content filling in either required section.	Complete the description by explaining what the PR does and how you verified the extensions.json configuration works correctly.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: adding an optimized extensions.json file for VSCode recommendations.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with 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.

Inline comments:
In @.vscode/optimized extensions.json:
- Around line 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.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ce671bac-8e1f-489a-b9e7-41afd7d33f3a

📥 Commits

Reviewing files that changed from the base of the PR and between b36759f and eef3a0c.

📒 Files selected for processing (1)

• .vscode/optimized extensions.json

[coderabbitai]

⚠️ 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:

• 1: https://code.visualstudio.com/docs/configure/extensions/extension-marketplace
• 2: https://dev.to/ayazar/recommend-visual-studio-code-extensions-along-with-your-code-5c8b
• 3: https://stackoverflow.com/questions/59519423/how-does-visual-studio-code-vscode-recommend-extensions-to-install-based-on-th

---

🏁 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.