Skip to content

feat(plugins): separate LSP servers into individual plugins#81

Merged
amondnet merged 5 commits into
mainfrom
feat/separate-lsp-plugins
Jan 29, 2026
Merged

feat(plugins): separate LSP servers into individual plugins#81
amondnet merged 5 commits into
mainfrom
feat/separate-lsp-plugins

Conversation

@amondnet

@amondnet amondnet commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add typescript-lsp plugin with official typescript-language-server
  • Add vue-lsp plugin with @vue/language-server
  • Add graphql-lsp plugin with graphql-language-service-cli
  • Add eslint-lsp plugin with @pleaseai/code wrapper
  • Update marketplace.json to register all 5 plugins
  • Remove deprecated reflexion plugin

Motivation

Users can now install LSP servers individually from marketplace based on their needs.

Test plan

  • Verify each plugin can be installed from marketplace
  • Test typescript-lsp with .ts files
  • Test vue-lsp with .vue files
  • Test graphql-lsp with .graphql files
  • Test eslint-lsp with JS/TS projects

Summary by cubic

Split LSP servers into standalone plugins so users can install only what they need from the marketplace. Adds TypeScript, Vue, GraphQL, and ESLint LSP plugins, removes the deprecated Reflexion plugin, and fixes logger output for bundled binaries.

  • New Features

    • Standalone plugins: typescript-lsp (typescript-language-server), vue-lsp (@vue/language-server), graphql-lsp (graphql-language-service-cli), eslint-lsp (@pleaseai/code wrapper).
    • Updated marketplace.json to register these plugins, renamed the collection to language-server-please, and pinned LSP package versions for stability.
  • Bug Fixes

    • Logger: switch to sync JSON output to stderr for bundled binaries to avoid ModuleNotFound errors (pino.destination({ fd: 2, sync: true })).

Written for commit f33b15d. Summary will update on new commits.

- Add typescript-lsp plugin with official typescript-language-server
- Add vue-lsp plugin with @vue/language-server
- Add graphql-lsp plugin with graphql-language-service-cli
- Update marketplace.json to register all plugins
- Remove reflexion plugin (already staged for deletion)

Users can now install LSP servers individually from marketplace.
Add standalone ESLint language server plugin using @pleaseai/code wrapper
which handles vscode-eslint download, build, and project validation.
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @amondnet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the modularity and user experience of Language Server Protocol (LSP) integrations. By separating various language servers into individual plugins, users gain greater control and flexibility, enabling them to customize their development environment by installing only the specific language support they require from the marketplace.

Highlights

  • New LSP Plugins: Dedicated plugins have been introduced for TypeScript, Vue, GraphQL, and ESLint Language Servers. This allows users to install and manage these language services individually based on their specific development needs.
  • Marketplace Update: The main marketplace configuration file, .claude-plugin/marketplace.json, has been updated. It now registers the new individual LSP plugins and reflects a renaming of the core 'code-please' plugin to 'language-server-please'.
  • Deprecated Plugin Removal: The 'reflexion' plugin, along with all its associated configuration and documentation files, has been completely removed from the repository. This streamlines the plugin ecosystem by removing an unused or superseded component.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request effectively separates various Language Server Protocol (LSP) servers into their own individual plugins, which is a great step towards a more modular and maintainable architecture. The changes are clear and align with the goal of allowing users to install LSP servers as needed. My main feedback across the new plugin configuration files is to pin the versions of the packages being installed via bunx. This is crucial for ensuring stability and reproducibility of the development environment, preventing unexpected issues from upstream package updates.

Comment thread plugins/eslint-lsp/.claude-plugin/plugin.json Outdated
Comment thread plugins/graphql-lsp/.claude-plugin/plugin.json Outdated
Comment thread plugins/typescript-lsp/.claude-plugin/plugin.json Outdated
Comment thread plugins/vue-lsp/.claude-plugin/plugin.json Outdated
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jan 29, 2026

Copy link
Copy Markdown

Deploying code-please with  Cloudflare Pages  Cloudflare Pages

Latest commit: f33b15d
Status:⚡️  Build in progress...

View logs

@codecov

codecov Bot commented Jan 29, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 38.62%. Comparing base (ef9504a) to head (f33b15d).
⚠️ Report is 5 commits behind head on main.

Files with missing lines Patch % Lines
packages/logger/src/index.ts 50.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #81      +/-   ##
==========================================
- Coverage   39.27%   38.62%   -0.65%     
==========================================
  Files          59       59              
  Lines        6503     6529      +26     
==========================================
- Hits         2554     2522      -32     
- Misses       3949     4007      +58     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@amondnet amondnet self-assigned this Jan 29, 2026
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

1 issue found across 10 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="plugins/graphql-lsp/.claude-plugin/plugin.json">

<violation number="1" location="plugins/graphql-lsp/.claude-plugin/plugin.json:12">
P2: bunx needs the graphql-language-service-cli package specified via `-p` because the executable is `graphql-lsp`, not `graphql-language-service-cli`. As configured, the command will fail to start the server.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Comment thread plugins/graphql-lsp/.claude-plugin/plugin.json Outdated
- typescript-language-server@^5.1.0
- @vue/language-server@^3.2.0
- graphql-language-service-cli@^3.1.0 (with -p flag for correct executable)
- @pleaseai/code@^0.1.0
Use pino.destination({ fd: 2, sync: true }) instead of pino.destination(2)
to avoid thread-stream worker which causes ModuleNotFound errors when
the binary is compiled with Bun and run on different machines.

The sync mode is slightly slower but ensures compatibility with
single-executable binaries where worker paths are hardcoded.
@amondnet
amondnet merged commit 62fd9e9 into main Jan 29, 2026
4 of 5 checks passed
@amondnet
amondnet deleted the feat/separate-lsp-plugins branch January 29, 2026 02:48
@passionfactory-bot passionfactory-bot Bot mentioned this pull request Jan 29, 2026
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