Use standalone @likec4/lsp package for language server#86
Conversation
Switch from `npx likec4 lsp` (full CLI) to `npx @likec4/lsp --yes` (standalone, zero-dependency LSP binary). The installer now checks for `npx` availability and offers to pre-install @likec4/lsp globally. See: likec4/likec4#2843 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Qodana Community for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2025.3.2
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe PR transitions the LikeC4 LSP server from a CLI-based approach to an npm package ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Summary
Switch from
npx likec4 lsp(full CLI package) tonpx @likec4/lsp --yes— the new standalone, zero-dependency LSP binary introduced in likec4/likec4#2843. The installer now checks fornpxavailability and offers to pre-install@likec4/lspglobally as a cache optimization.Changes
npx @likec4/lsp --yes --stdio, removedNODE_ENV=developmentand legacy CLI flags (--no-color,--log-level=error)npxinstead oflikec4, updated install command and notification textTest plan
.c4file and verify LSP starts and provides completions/diagnosticsnpm install -g @likec4/lsp🤖 Generated with Claude Code