Editor Setup

VS Code

Nulang ships a VS Code extension with syntax highlighting, diagnostics, hover, go-to-definition, references, rename, completion, signature help, inlay hints, formatting, and more — powered by the built-in language server (nulang --lsp).

Marketplace

The repository has a publishing workflow for the VS Code Marketplace and Open VSX, but this page does not assert that publication succeeded. Search for “Nulang” in your editor’s extension marketplace; if no verified listing is available, use the .vsix instructions below.

Install a local .vsix

The extension lives in the repo at editors/vscode/:

git clone https://github.com/nulang-org/nulang.git
cd nulang/editors/vscode
npm ci
npx @vscode/vsce package
code --install-extension nulang-0.2.0.vsix

Development setup

The extension source contains integration tests. If you are developing the extension, build it and install the resulting .vsix rather than copying uncompiled source files into the VS Code extensions folder.

Requirements

Install a prebuilt release binary for your platform first. The nulang binary must be on your PATH, or point NULANG_PATH at it, or set the nulang.path setting explicitly (setting > NULANG_PATH > PATH). Useful commands (Command Palette → “Nulang: …”): Compile, Run, Type Check, and Restart Language Server.

Other editors

Any editor with LSP client support can talk to nulang --lsp over stdio (Neovim nvim-lspconfig, Emacs lsp-mode/eglot, Helix, Zed). Point your LSP client at nulang --lsp for .nula files. See Language Server & Tooling for the full feature list and per-editor configuration.