Rua Language — VS Code extension

Editor support for Rua (Rust-like syntax that transpiles to Lua 5.5), backed by the rua-lsp language server from this workspace.

Features

Provided by the rua-lsp server (see crates/rua-lsp):

• Live diagnostics (type/parse errors)
• Hover, go-to-definition, find references, rename (cross-file)
• Document symbols / outline
• Completion: members (x.), paths (Type::), globals + keywords
• Document formatting

Plus TextMate syntax highlighting and basic editing config (comments, brackets, auto-close) from this extension.

Bundled toolchain

Release VSIX files include rua-lsp and ruac for these platforms:

• Linux x64 and arm64
• macOS arm64
• Windows x64

macOS x64 (Intel) is not bundled. To use Rua on that platform, set rua.server.path and rua.compiler.path to locally installed binaries.

The extension selects the matching binary automatically. The rua.server.path and rua.compiler.path settings override the bundled binaries when they are non-empty, which is useful when developing a local compiler build.

For local development, build the tools in the repository first:

The rua-lsp binary is behind the lsp feature, so pass --features lsp:

# from the rua workspace root
cargo build -p rua-lsp --bin rua-lsp --features lsp             # debug   -> target/debug/rua-lsp
cargo build -p rua-lsp --bin rua-lsp --features lsp --release   # release -> target/release/rua-lsp
cargo build -p ruac                                             # debug   -> target/debug/ruac
cargo build -p ruac --release                                   # release -> target/release/ruac

Then point the extension at them, e.g.:

{
  "rua.server.path": "${workspaceFolder}/target/debug/rua-lsp",
  "rua.compiler.path": "${workspaceFolder}/target/debug/ruac"
}

If both tools are on PATH, set the corresponding settings to rua-lsp and ruac to use them instead of the bundled binaries.

Develop / debug

cd editors/vscode
npm install
npm run compile      # or: npm run watch
npm run test-extension

Press F5 ("Run Rua Extension") to launch an Extension Development Host, then open any .rua / .ruai file.

Package a .vsix

npm run package      # produces rua-lang-<version>.vsix

The release workflow builds the native toolchain in parallel and places it under bin/<platform>/ before running this command. A manually packaged VSIX only contains binaries that have already been staged in that directory.

The repository workflow at .github/workflows/vscode-release.yml runs for v* tags and also supports manual builds. Before tagging a release:

1. Update the extension version in package.json.
2. Create a repository secret named VSCE_PAT with Marketplace publish scope.
3. Commit and push a matching tag, for example v0.1.1.

The workflow builds every supported platform, assembles one VSIX, uploads it as a workflow artifact, and publishes it to the Visual Studio Marketplace for a tag push. A manual workflow run only builds and uploads the VSIX.

Settings

To make the context-menu command emit a project module tree when it is invoked on the root source file:

{
  "rua.compiler.args": ["--emit", "modules", "--out-dir", "dist/modules"]
}

Configure runtime search directories in .ruarc.toml; ruac writes them into the generated root module's package.path:

[runtime]
lua_path = ["./dist/modules", "./lua"]

Alternatively set LUA_PATH in the host process or append repeated --lua-path <dir> compiler arguments. Child source modules are not independent compiler entry points; use the command on the project root file.

Restart waits for the server child process close event before disposing its output channel and watcher.

Project libraries should normally be stored in .ruarc.toml at the workspace root so ruac and rua-lsp consume the same inputs:

[workspace]
library = ["./types"]

[[workspace.lua_library]]
root = "../moon_rs/lualib"

[workspace.library_mounts]
host = "../host/host.ruai"

[runtime]
std_path = "./std"
lua_path = ["./dist/modules", "./lua"]

workspace.lua_library is the preferred bulk configuration for ordinary Lua libraries. With colocated files, moon/http/client.ruai automatically describes require("moon.http.client"). For separate trees, use one entry with declaration_root and runtime_root; no per-module mapping is needed.

All project fields use snake_case. Library and standard-library inputs are configured only in .ruarc.toml; VS Code settings only control the compiler and language-server processes plus protocol tracing. The extension watches .ruarc.toml and asks the server to reload it after changes.

Commands

• Rua: Build File (rua.buildFile): saves and builds the selected .rua file. Available from Explorer and editor context menus.
• Rua: Restart Language Server (rua.restartServer)