"Clojure lsp – One tool to lint them all"
summary
Clojure-lsp exposes diagnostics, formatting and namespace cleanup as a CLI and API so teams run the same checks in editors and CI; it uses clj-kondo for analysis, cljfmt for formatting and a dump feature to export dependency/namespace graphs. Nubank applies a centralized code-style jar across ~1,300 Clojure services and ~1,800 engineers, automates weekly library bumps with bumpito, and adds custom linkers/hooks to detect real bugs (eg. wrong date-pattern strings) before deploy.
AI-written summary · about
chapters (10)
- 0:00Intro
- 3:36Overview
- 6:09Explanation
- 9:22Closure LSP
- 12:50Main Features
- 17:17How to use
- 18:54Exportable configurations
- 24:55Bumpito
- 25:59Custom linkers
- 32:00Conclusion
related talks
21mLLMs + Clojure = Who needs frameworks?
40mTargeting Clojure & ClojureScript from a Single Codebase
24mBuilding Intelligible Systems
27mHow to Increase Clojure Outreach
42mWhy Clojure?
41mClojureScript for Skeptics
38mProduction Ready ClojureScript: Tales from the Frontier
40mGetting 50,000 Companies on Board with Clojure