Skip to content

Conversation

@rodmk
Copy link
Owner

@rodmk rodmk commented Feb 12, 2026

Summary

  • Make trailing-comma removal string-aware by moving it into the state-machine loop
  • Add regression test for the edge case

This PR is for running CI in the fork before updating coder/registry#707.

🤖 Generated with Claude Code

rodmk and others added 3 commits February 7, 2026 18:22
…alls

The auto_install_extensions feature uses `sed | jq` to parse
.vscode/extensions.json, but this file is JSONC (JSON with Comments),
not strict JSON. The current parser fails on:

- Block comments (/* */)
- Trailing commas (common in VS Code-generated files)
- URLs inside string values (sed mangles https:// to https:)

Replace the sed|jq pipeline with a proper state-machine JSONC parser
that runs on the bundled Node.js binary already shipped with both
code-server and vscode-web. This eliminates the jq dependency for this
feature.

Also batch extension installs into a single invocation using repeated
--install-extension flags instead of spawning one process per extension.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Move trailing-comma handling into the state-machine loop so it never
modifies characters inside quoted strings. Adds a regression test for
the edge case (though it can't occur in practice since extension IDs
are restricted to [a-z0-9-] by vsce's nameRegex).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

1 participant