Skip to content

chore: remove the VS Code extension client, keep the LSP server - #104

Merged
FIERsity merged 1 commit into
mainfrom
chore/remove-vscode-extension
Aug 6, 2026
Merged

chore: remove the VS Code extension client, keep the LSP server#104
FIERsity merged 1 commit into
mainfrom
chore/remove-vscode-extension

Conversation

@FIERsity

@FIERsity FIERsity commented Aug 6, 2026

Copy link
Copy Markdown
Owner

Cuts the VS Code extension client (post-release-plan C5, pulled forward on user request): vscode/ + npm deps + version sync + vsce gate check removed; envorigin lsp server kept (pure Rust, any LSP editor attaches). release.sh loses the npm bump, check-release-ready.sh goes 8→7 gates, docs (README/CONTRIBUTING/ARCHITECTURE) and Cargo.toml exclude synced, CHANGELOG [1.12.0] gains a Removed entry.

Rationale: low-frequency-edited config files → low LSP value density; never on the marketplace; only feature with an npm toolchain.

Verified: 145 tests green, clippy -D warnings clean, both scripts pass bash -n.

🤖 Generated with Claude Code

The extension was the weakest value/cost ratio in the product: env
config files are low-frequency-edited (live diagnostics add little),
it was never on the marketplace (invisible to users), and it was the
only feature dragging in an npm toolchain and a gate check.

Removed: vscode/ (TS client + lockfile + vsix), the npm version bump
in release.sh, the vsce packaging check in check-release-ready.sh
(8 gates → 7), Cargo.toml exclude entry, and the README/CONTRIBUTING/
ARCHITECTURE extension docs. CHANGELOG [1.12.0] gains a Removed entry.

Kept: `envorigin lsp` — pure Rust, shares the analyzers; any
LSP-capable editor (Neovim, Emacs, JetBrains) can attach.

Co-Authored-By: Claude <noreply@anthropic.com>
@FIERsity
FIERsity merged commit b422502 into main Aug 6, 2026
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@FIERsity, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cfa5cf78-25a6-4667-9136-87ac6fe5acae

📥 Commits

Reviewing files that changed from the base of the PR and between 3baf2e3 and c37eb3a.

⛔ Files ignored due to path filters (1)
  • vscode/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (12)
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CONTRIBUTING.md
  • Cargo.toml
  • README.md
  • docs/post-release-plan.md
  • scripts/check-release-ready.sh
  • scripts/release.sh
  • vscode/README.md
  • vscode/package.json
  • vscode/src/extension.ts
  • vscode/tsconfig.json

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

Comment @coderabbitai help to get the list of available commands.

@FIERsity
FIERsity deleted the chore/remove-vscode-extension branch August 6, 2026 20:35
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