A Language Server for Clojure. Taking a Cursive-like approach of statically analyzing code.
The goal of this project is to bring great editing tools for Clojure to all editors. It aims to work alongside you to help you navigate, identify and fix errors, perform refactors and much more!
You will get:
- Jump to definition
- Find references
- Code actions
- Automatic ns management
- Code lens
- Semantic tokens (syntax highlighting)
- You need
javaon your $PATH.
- Grab the latest
clojure-lspfrom github LATEST
- Place it in your $PATH with a chmod 755
- Follow the documentation for your editor's language client. See Clients below.
clojure-lsp is available in the nixpkgs:
nix-shell -p clojure-lsp
For building manually, run
lein bin to generate the binary inside
target folder or
lein uberjar for building the standalone jar.
clojure-lsp development, there are 3 possible ways of finding a bug or implementing a new feature:
- Create a test for your bug/feature, then implement the code following the test.
clojure-lspstarts a NREPL server, with that it's possible to change the code of a running instance and see the changes on your client in real time. To get the NREPL port, you can check the
/tmp/clojure-lsp.outlog, it will print the NREPL port on server startup or you can get it via
server-infocustom LSP command.
clojure-lspwith your changes and test it manually in your client, this is the slowest option, but it makes sense final tests.
- For debugging purposes, there is two custom commands
clojure-lsp are very welcome! You can open an issue or a PR and we'd love to help.
Support the project
clojure-lsp has more than 8.000 lines of code, to keep all of this working, we need to help the community on a lot of issues and implement new features. As a LSP server, this project is the base for Clojure clients like Emacs(lsp-mode), VSCode(Calva) and vim.
You can help us keep going and improving it by supporting the project