.vsix file directly. You can also build it yourself from source. Both methods take only a few minutes.
This extension is not on the VS Code Marketplace. Every release is published to GitHub with the packaged
.vsix attached.From a release
1
Download the VSIX
Grab
glua-lsp-<version>.vsix from the latest release.2
Install it
Run this from the folder you saved the file in.Or from inside the editor: Extensions → the
··· menu → Install from VSIX…3
Open a GLua file
The extension activates when you open a
.lua file in a Garry’s Mod workspace.Updating
A.vsix install does not auto-update. Download the newer file and run the same install command — it replaces the previous version in place.
To hear about new versions, watch the repository: Watch → Custom → Releases.
Unreleased builds
Every push tomain builds and attaches a .vsix to its CI run, so you can pick up a fix before it is tagged. Open the latest CI run, scroll to Artifacts, and download glua-lsp-vsix-<sha>.
GitHub wraps workflow artifacts in a
.zip. Unzip it to get the .vsix inside.From source
1
Clone and install dependencies
Clone the repository and install packages with pnpm.
2
Build and package
Compile the extension and produce a That writes
.vsix.packages/glua-lsp/glua-lsp-<version>.vsix.3
Run or install
Press F5 to launch the extension in a new Extension Development Host window, or install the package you just built.
Verify the installation
Open any.lua file inside a Garry’s Mod addon folder. The VS Code status bar should show a realm label such as GLua · Server. If you see that label, the language server is active and indexing your workspace.
Setting it as your formatter
To format GLua files with the extension, register it as the default formatter for theglua language in your user or workspace settings.json:
Requirements
- VS Code 1.85 or newer
- No network connection required at runtime (the full wiki dataset is bundled)
- No additional dependencies or external tools needed