Skip to content

Install VS Code extensions in the dev container - #51

Merged
DetweilerRyan merged 2 commits into
mainfrom
chore/devcontainer-extensions
Nov 21, 2026
Merged

DetweilerRyan merged 2 commits into
mainfrom
chore/devcontainer-extensions

Conversation

@DetweilerRyan

@DetweilerRyan DetweilerRyan commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

Adds four VS Code extensions to the dev container, as #49 asks, and allows the VS Code Marketplace in the kit's network policy so the container can install them.

What to look at

  • .devcontainer/devcontainer.json: the new customizations.vscode.extensions list, with a comment on each entry saying what it is for.
  • .sbx-kits/splitsmart/splitsmart.yaml: three new runtime allow entries, marketplace.visualstudio.com:443, '*.gallery.vsassets.io:443' and '*.gallerycdn.vsassets.io:443'.
  • .sbx-kits/splitsmart/README.md: a pointer to the extension list, and the new hosts in "Network and credentials".

Decisions made

  • Wildcard publisher subdomains instead of one host per extension. Each extension's files download from its publisher's own subdomain, such as oxc.gallerycdn.vsassets.io; I read those hosts from the gallery API's asset URLs. The kit spec says *.example.com matches exactly one label, which covers these hosts. Alternative: list each publisher's two hosts. That is narrower, but adding an extension would also mean editing the policy, and the two lists would drift.
  • Oxc gets no editor settings. The extension is installed, but editor.defaultFormatter and format-on-save aren't set in customizations.vscode.settings. Alternative: set oxfmt as the default formatter in the container. That changes how saving behaves for everyone, so I left it for a separate change if you want it.
  • Branch kind is chore/, because no existing branch kind fits a dev-environment change.

For the owner to confirm

Nothing. You approved adding the Marketplace hosts to the policy in the session.

Changed test expectations

Nothing.

Verification

  • npm run lint, npm run format:check, npm run typecheck, npm test and npm run build each exited 0 in the worktree after both commits.
  • I looked up each extension ID in the Marketplace gallery API. All four exist, from the expected publishers (jackiotyu, oxc, Vitest, GitHub).
  • splitsmart.yaml parses with PyYAML. The allow list has nine plain strings, with the wildcard entries quoted.
  • Not verified: rebuilding the sandbox from the updated kit, and rebuilding the dev container to see the extensions install. Both need the host's sbx and VS Code with Dev Containers, which this session doesn't have.

Links

Closes #49

🤖 Generated with Claude Code

@vercel

vercel Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
split Ready Ready Preview Nov 21, 2026 9:13pm UTC

agent and others added 2 commits November 21, 2026 16:13
Adds Git Worktree Manager, Oxc, Vitest and GitHub Pull Requests under
customizations.vscode.extensions, and points the kit README at the list.

Closes #49

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dev container installs its extensions from marketplace.visualstudio.com
and each publisher's subdomain of gallery.vsassets.io and
gallerycdn.vsassets.io.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DetweilerRyan
DetweilerRyan force-pushed the chore/devcontainer-extensions branch from 545a13c to 94dbf65 Compare November 21, 2026 21:13
@DetweilerRyan
DetweilerRyan merged commit f88b4e4 into main Nov 21, 2026
3 checks passed
@DetweilerRyan
DetweilerRyan deleted the chore/devcontainer-extensions branch November 21, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Git Worktree Manager, Oxc, Vitest, and GitHub Pull Requests extensions to the dev container

1 participant