use likec4-lsp as the LSP command#4
Conversation
Signed-off-by: spaasis <17126867+spaasis@users.noreply.github.com>
📝 WalkthroughWalkthroughUpdated the LSP language server invocation in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@lsp/likec4.lua`:
- Around line 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| -- This assumes 'likec4-lsp' is in your system's PATH. | ||
| -- https://likec4.dev/tooling/editors/#standalone-language-server | ||
| cmd = { "likec4-lsp", "--stdio" }, |
There was a problem hiding this comment.
🧩 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:
- 1: https://likec4.dev/tooling/editors/
- 2: https://npm.io/package/@likec4/language-server
- 3: https://likec4.dev/tooling/cli/
- 4: https://github.com/likec4/likec4/blob/main/CHANGELOG.md
- 5: https://registry.npmjs.org/likec4
- 6: https://newreleases.io/project/github/likec4/likec4/release/v1.54.0
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/lsppackage for the standalone binary, or - Switch to
likec4 lsp --stdioif they have the mainlikec4CLI 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.
1 participant
By the documentation
likec4-lspis the command to use. Tested on my machine - runningnpm install -g @likec4/lspadded thelikec4-lspcommand, and using that in this plugin made the LSP attach properly