JETLS.jl documentation
The goal of this project is to develop a new language server for Julia, currently called "JETLS". JETLS aims to enhance developer productivity by providing advanced static analysis and seamless integration with the Julia runtime. By leveraging tooling technologies like JET.jl, JuliaSyntax.jl and JuliaLowering.jl, JETLS aims to offer enhanced language features such as type-sensitive diagnostic, macro-aware go-to definition and such.
JETLS is under active development. Not production-ready; APIs and behavior may change. Stability and performance are limited. Expect bugs and rough edges.
Server installation
Editor clients for JETLS generally do not bundle the JETLS server itself. You need to install the jetls executable separately before using any editor integration.
Prerequisites
JETLS requires Julia v"1.12" or higher (1.12.2+ recommended).
Installing the jetls executable
All editor integrations require the jetls executable app, which is the main entry point for running JETLS.
Install it with:
julia -e 'using Pkg; Pkg.Apps.add(; url="https://github.com/aviatesk/JETLS.jl", rev="release")'This will install the jetls executable to ~/.julia/bin/. Make sure ~/.julia/bin is available on the PATH environment so the executable is accessible.
You can verify the installation by running:
jetls --helpIf this displays the help message, the installation was successful and ~/.julia/bin is properly added to your PATH.
To update JETLS to the latest version, re-run the installation command:
julia -e 'using Pkg; Pkg.Apps.add(; url="https://github.com/aviatesk/JETLS.jl", rev="release")'To pin a specific version instead, use the release tag rev="YYYY-MM-DD":
julia -e 'using Pkg; Pkg.Apps.add(; url="https://github.com/aviatesk/JETLS.jl", rev="2025-11-25")'Editor setup
After installing the jetls executable, set up your editor to use it.
VSCode
jetls-client is a VSCode client extension for JETLS.
Install the jetls-client extension from the VSCode Extensions marketplace (search for "JETLS Client" from the extensions view), then open any Julia file. The extension will automatically use the jetls executable from your PATH.
For advanced launching configurations and JETLS behavior settings, see the jetls-client README.
Currently, JETLS.jl is not integrated with the julia-vscode extension. To use JETLS from VSCode, install the jetls-client extension. While we generally recommend disabling julia-vscode when using jetls-client, this is not required; you can use both julia-vscode and jetls-client in the same VSCode session. However, since the LSP features provided by JETLS.jl differ in both type and quality from those provided by julia-vscode's language server backend (LanguageServer.jl), you may encounter confusing situations where, for example, completion candidates are provided from different backends.
Emacs
Minimal Emacs (eglot client) setup:
(add-to-list 'eglot-server-programs
'(((julia-mode :language-id "julia")
(julia-ts-mode :language-id "julia"))
"jetls"
"--threads=auto"
"--"
"--socket"
:autoport))Vim
Minimal Vim setup using the Vim9 LSP plugin
call LspAddServer([#{name: 'JETLS.jl',
\ filetype: 'julia',
\ path: 'jetls',
\ args: [
\ '--threads=auto',
\ '--'
\ ]
\ }])Neovim
Minimal Neovim setup (requires Neovim v0.11):
vim.lsp.config("jetls", {
cmd = {
"jetls",
"--threads=auto",
"--",
},
filetypes = {"julia"}
})
vim.lsp.enable("jetls")Sublime
Minimal Sublime setup using the Sublime-LSP plugin and modifying the LSP.sublime-settings file:
{
"clients": {
"jetls": {
"enabled": true,
"command": ["jetls", "--threads=auto", "--", "--socket=${port}"],
"selector": "source.julia",
"tcp_port": 0
}
}
}Zed
Zed extension for Julia/JETLS is available: See aviatesk/zed-julia#avi/JETLS for the detailed installation steps.
Helix
Minimal Helix setup:
languages.toml
[[language]]
name = "julia"
language-servers = [ "jetls" ]
[language-server]
jetls = { command = "jetls", args = ["--threads=auto", "--"] }Advanced: using local JETLS checkout
Advanced users can run JETLS directly from a local checkout by replacing the jetls executable with julia -m JETLS:
julia --startup-file=no --project=/path/to/JETLS -m JETLSWhen using a local checkout other than the release branch (e.g. master), JETLS dependencies may conflict with the dependencies of the code being analyzed. The release branch avoids this by vendoring dependencies with rewritten UUIDs.