Skip to content

use likec4-lsp as the LSP command #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
spaasis wants to merge 1 commit into
base: main
Choose a base branch
from
Open

use likec4-lsp as the LSP command #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions lsp/likec4.lua
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
return {
-- The command to start the language server.
-- This assumes 'likec4' is in your system's PATH.
cmd = { "likec4", "lsp", "--stdio" },
-- This assumes 'likec4-lsp' is in your system's PATH.
-- https://likec4.dev/tooling/editors/#standalone-language-server
cmd = { "likec4-lsp", "--stdio" },
Comment on lines +3 to +5
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 22, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Does likec4 provide a standalone likec4-lsp binary, and what is the correct command syntax to start it?

💡 Result:

Yes, LikeC4 provides a standalone likec4-lsp binary via the @likec4/lsp npm package (new in v1.54.0, April 2026) or previously via the main likec4 CLI and @likec4/language-server package. To install and start: 1. Global install: npm install -g @likec4/lsp (provides likec4-lsp binary, self-contained with zero dependencies). 2. Or install main CLI: npm install -g likec4 (provides likec4 lsp command). Correct command syntax (one transport option required): - likec4-lsp --stdio - likec4 lsp --stdio - likec4 lsp --node-ipc - likec4 lsp --socket=3000 - likec4 lsp --pipe /tmp/likec4.pipe Additional options: --watch (enable watcher), --no-manual-layouts, --use-dot. Note: Older @likec4/language-server provided likec4-language-server --stdio but is now internal/deprecated in favor of main likec4 package or new @likec4/lsp.

Citations:

Document migration path for the breaking change to standalone binary.

The change to likec4-lsp --stdio is technically correct (the standalone binary exists via the @likec4/lsp npm package as of v1.54.0) and the command syntax is valid per the official documentation.

However, this remains a breaking change for existing users: those with the likec4 CLI installed but not the new @likec4/lsp package will lose LSP functionality after upgrading. Ensure release notes clearly document that users must either:

  • Install the new @likec4/lsp package for the standalone binary, or
  • Switch to likec4 lsp --stdio if they have the main likec4 CLI installed
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@lsp/likec4.lua` around lines 3 - 5, The change to use the standalone binary
in the LSP config (cmd = { "likec4-lsp", "--stdio" }) is a breaking change for
users who only have the main likec4 CLI; update the project’s release notes and
this file’s top comment to document the migration path: state that users can
either install the new `@likec4/lsp` package to get the likec4-lsp binary or
continue using the main CLI by configuring the command as likec4 lsp --stdio
(e.g., cmd = { "likec4", "lsp", "--stdio" }) and include exact install
instructions (npm install -g `@likec4/lsp`) and a short sentence about versions
(since v1.54.0) so users know when the standalone binary became available.


-- The filetypes for which this server should be enabled.
filetypes = { "likec4" },
Expand Down