TARUS

A VS Code extension — coding assistant for TAURI® apps.
Navigation, autocomplete, diagnostics, and symbols for commands and events.

Introduction

In Tauri projects, it’s often difficult to quickly navigate between the frontend and the Rust backend and understand where a command is defined or called. This extension is designed to make that navigation fast and effortless, allowing you to jump between the frontend and backend parts of the project in both directions. As secondary features, the extension can also detect unused commands and help autocomplete command names while typing.

Features

Symbols

Workspace Symbols (Ctrl+T) — Search commands/events across entire project.

Import Aliases

TARUS fully supports import aliases, a common JavaScript/TypeScript pattern:

import { invoke as myInvoke, emit as sendEvent } from "@tauri-apps/api/core";

// These will be correctly recognized
await myInvoke("my_command");
sendEvent("my_event");

Type Generation Support

TARUS works with popular type generation libraries for Tauri: tauri-specta, specta-typescript, ts-rs, and tauri-typegen. When generated binding files are present, all the same features — navigation, CodeLens, hover, references, autocomplete, and diagnostics — extend to cover type information as well. This includes parameter key validation, return type checking, and event payload type verification with quick-fix code actions.

Generator output paths are discovered automatically from your existing project configs (tauri.conf.json, .cargo/config.toml, Rust source files) — no extra setup required.

Specta's typed event API (events.X.listen/emit/once) is also fully supported.

Extension Settings

This extension contributes the following settings:

• tarus.developerMode (boolean): Enables detailed logging and internal diagnostics (for extension developers). Requires VS Code restart. Default: false.
• tarus.referenceLimit (number): The maximum number of individual file links to show in CodeLens before summarizing them (e.g., '5 references'). Minimum value is 0. Default: 3.

Supported Languages

TARUS supports the following languages and frameworks:

Advanced: Tree-sitter Queries

TARUS uses Tree-sitter for parsing source code. The parsing patterns are defined in .scm query files located in lsp-server/src/queries/:

Query File Structure

Query files use S-expression syntax to match AST patterns. Example from rust.scm:

; Match #[tauri::command] fn name()
(
  (attribute_item
    (attribute
      (scoped_identifier
        path: (identifier) @_attr_path
        name: (identifier) @_attr_name)))
  .
  (function_item
    name: (identifier) @command_name)
  (#eq? @_attr_path "tauri")
  (#eq? @_attr_name "command")
)

Customizing Queries

If you need to support custom patterns (e.g., wrappers around Tauri APIs), you can modify the query files:

1. Clone the repository
2. Edit the relevant .scm file in lsp-server/src/queries/
3. Rebuild the LSP server: cargo build --release --manifest-path lsp-server/Cargo.toml
4. Replace the binary in extension/bin/

Note: Query files are embedded at compile time, so changes require rebuilding the server.

License

MIT © 2026 mvoof

TAURI is trademark of [The Tauri Programme within the Commons Conservancy]