iris-lsp language server brings Iris Code to those editors. It runs on your machine and needs neither Node.js nor a network connection to analyse your code.
Installing
Download the program for your platform from the releases page, make it executable, and put it in a folder on yourPATH so your editor can find it.
Verifying the download
Every release includes aSHA256SUMS file, a list of fingerprints for the downloads. Check the file you downloaded against it before you put it on your PATH, to confirm it arrived complete and unchanged.
shasum -a 256 --check --ignore-missing SHA256SUMS.
Configuration
Neovim
Neovim 0.11 and newer can configure a language server without any plugin:jproperties is in the list because Iris Code checks .properties files for passwords and keys committed by mistake, which is the only thing it checks in them. Remove it if you would rather not run the server on those files.
Iris Code adds to your existing language server rather than replacing it, so turn it on alongside whichever one already handles your language. Neovim runs several at once and combines their diagnostics, the warnings shown in the code.
Helix
Inlanguages.toml:
"iris" to the language-servers list of every language you want covered. Helix also runs several servers per language, so your existing one stays in place.
What you get
These features come from the language server itself, so they work in any editor that supports LSP:- inline diagnostics for health, complexity, duplication, naming, hardcoded secrets and the nine security smell categories
- the file’s health score on hover
- code lenses on long functions, where the client renders them
- quick fixes that scaffold an
iris-ignoresuppression with its required reason - filename-convention renames
- configuration read from the same
.irisconfig.json, reloaded when that file changes
iris-lsp --panel <dir>serves the full Iris Code panel as a local web page and prints its address.iris-lsp --dashboard <dir>serves a one-page summary of the workspace.
127.0.0.1), at an address with a random path that changes each run.
Signing in
One sign-in covers the language server, the CLI (theiris terminal commands) and the JetBrains plugin. All three read ~/.iris/credentials.
--licence-status errs on the safe side: if it cannot work out your licence, it reports that you do not have Pro rather than assuming you do.
Enforcement without Node
The gate is the pass-or-fail check against your configured limits. It is built into the program, so a repository can be checked on a machine with no Node.js installed:0 on a pass and 1 on a failure, which is all a git hook or a CI step needs to allow or stop a change. See the git hook and CI enforcement for how that fits into a workflow.
Free and Pro
Diagnostics, hover, quick fixes and renames are free. The gate, and the Pro rules behind it, need a licence. Without one,--check reports what it can but does not apply the Pro limits. See Pro for the split.