Tools

Editors and browser tools

Every editor here talks to the same two programs, built into the quillo binary: quillo lsp, the language server, and quillo dap, the debugger. Install quillo, then the plugin for your editor.

Editors and IDEs

VS Code

Highlighting, diagnostics as you type, quick fixes, hover, go to definition, completion, parameter hints, the outline, end tags as you type, snippets, a debugger for the server and the browser side, and Quillo: New program.

  • Highlighting
  • Language server
  • Debugger
  • Snippets
  • Run and check
VSCodium, Cursor, Windsurf and Gitpod take the same extension, as its .vsix until it is on Open VSX.

JetBrains IDEs

IntelliJ IDEA, WebStorm, PyCharm and the others from 2025.3, and Android Studio from Rabbit 2: VS Code's grammars, the language server through LSP4IJ, live templates, run configurations and a debugger.

  • Highlighting
  • Language server
  • Debugger
  • Snippets
  • Run and check

Zed

tree-sitter-quillo for highlighting, the outline and brackets; quillo lsp; and a Quillo debugger through quillo dap.

  • Highlighting
  • Language server
  • Debugger

Neovim

Filetypes, tree-sitter-quillo through nvim-treesitter, quillo lsp through vim.lsp.config, and nvim-dap.

  • Highlighting
  • Language server
  • Debugger

Helix

A languages.toml entry with tree-sitter-quillo, its queries and textobjects, quillo lsp and quillo dap.

  • Highlighting
  • Language server
  • Debugger

Emacs

quillo-ts-mode on tree-sitter-quillo (Emacs 29 and later) or quillo-mode without it, eglot for quillo lsp and dape for quillo dap.

  • Highlighting
  • Language server
  • Debugger

Sublime Text

VS Code's grammars, quillo lsp through the LSP package, and a build system that runs and checks the file.

  • Highlighting
  • Language server
  • Run and check

Vim

A syntax file, indentation and :make with quillo check, with no language server needed; and the setup for Vim's LSP clients.

  • Highlighting
  • Run and check

Eclipse

VS Code's grammar through TM4E, and quillo lsp and quillo dap through LSP4E, set up by hand.

  • Highlighting
  • Language server
  • Debugger

Visual Studio

VS Code's grammar in Visual Studio's own TextMate folder, for highlighting. The language server needs an extension that is not there yet.

  • Highlighting

In the browser

Quillo DevTools

A Quillo panel in the developer tools of Chrome and Edge (111 and later), for pages Quillo makes: the components on the page with their props and state, and where each prop comes from; the server fn calls it makes; live updates; the errors Quillo catches; and the server's health and query times.

  • Components
  • Calls
  • Live
  • Errors
  • Server

Until it is in the browsers' stores: chrome://extensions (or edge://extensions), Developer mode, Load unpacked, and the repository's extension/ folder. Firefox is not supported yet.

For documentation and books

tree-sitter-quillo

The grammar Zed, Neovim, Helix and Emacs use, with its queries: every .qwe file of Quillo's repositories parses with it.

Shiki

The TextMate grammar for Shiki: VitePress, Astro, Nuxt Content.

highlight.js

A language definition for highlight.js 11.

Prism

A language definition for Prism: Docusaurus, Gatsby.

pandoc and Kate

A KDE syntax file, for Kate and for pandoc's printed books.

Any other editor

An editor that speaks the Language Server Protocol can run quillo lsp on stdin and stdout, for diagnostics, completion, hover, go to definition, references, rename and signature help; one that speaks the Debug Adapter Protocol can run quillo dap, with the launch fields program, args, cwd and stopOnEntry. See Install and the editors repository.

Logos from Simple Icons (CC0); each is the trademark of its owner, shown to say that Quillo works with it. VS Code, Visual Studio and Edge, which Simple Icons does not carry, and the highlighters are shown with a plain icon.