A Visual Studio Code extension providing Clojure and ClojureScript language support with REPL integration, code completion, and formatting.
clojureVSCode is a Visual Studio Code extension that adds full-featured Clojure and ClojureScript language support to the editor. It solves the problem of fragmented Clojure tooling by integrating REPL interaction, code completion, navigation, formatting, and testing directly into VS Code's interface.
Clojure and ClojureScript developers who use Visual Studio Code as their primary editor and want a streamlined, integrated development experience without switching between tools.
Developers choose clojureVSCode because it brings the powerful interactive development workflow of Clojure (via nREPL) into the familiar and extensible VS Code environment, with robust features like intelligent code completion, formatting, and test integration out of the box.
Clojure support for Visual Studio Code
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly connects to nREPL sessions for live code evaluation, enabling interactive development directly within VS Code, as highlighted in the Quickstart and REPL integration features.
Provides code completion, navigation to definitions, and documentation hover, with examples shown in the Supported Features section for enhanced productivity.
Uses cljfmt to format Clojure code automatically, configurable via settings like 'clojureVSCode.formatOnSave' to maintain consistency across projects.
Supports running and managing Clojure unit tests within the editor, streamlining testing workflows without external tools.
ClojureScript requires manual nREPL setup with extra commands, as admitted in the ClojureScript Project Setup section, making it less user-friendly than Clojure.
The README explicitly lists linting and debug as unsupported features, which are common in other language extensions and can hinder code quality and troubleshooting.
Setting up dependencies in profiles.clj or project.clj is necessary for full functionality, adding overhead for new users or teams, as noted in the Manual Configuration section.