glslint — VS Code / Cursor extension
A thin LSP client that runs the glslint binary in lsp mode and surfaces its diagnostics on GLSL files. It also ships GLSL syntax highlighting (a TextMate grammar) plus bracket/comment editing config. Works in VS Code and Cursor (identical extension API).
Setup
The extension resolves the glslint binary in this order: an explicit glslint.path setting → a local install (~/.cargo/bin/glslint, then PATH) → otherwise it downloads the prebuilt binary for your platform from this repo's GitHub Release and caches it in the extension's storage. So the only hard requirement is glslangValidator (glslint shells out to it):
brew install glslang
To use a local build instead of the downloaded one — recommended while hacking on glslint — install it:
cargo install --path . # release binary into ~/.cargo/bin/glslint
Then install the client's dependency:
cd editors/vscode && npm install
Run it
- Dev host (fastest): open the
editors/vscode folder in VS Code/Cursor and press F5. That launches an Extension Development Host; open your deck-wind-layer folder in it and open a shader (e.g. src/shaders/draw.vert.glsl).
- Install for real:
npx @vscode/vsce package here, then install the resulting .vsix (code --install-extension glslint-0.1.0.vsix).
If you didn't cargo install (e.g. you want the debug binary), point the setting at it:
{ "glslint.path": "/absolute/path/to/glslint/target/debug/glslint" }
What you should see
Open draw.vert.glsl and change a uniform-block member to a typo, e.g. wind.maxSpeed → wind.maxSpeeed. A red squiggle appears under it:
'maxSpeeed' : no such field in structure 'wind'
That's the point of glslint: wind is declared in a separate windUniforms.glsl module that stock GLSL tools never see, so only glslint can validate the member access. Diagnostics are debounced and map back to the exact file:line:col, including into the injected module files when the error originates there.
Hover a uniform-block member like wind.uMin to see its type, and cmd-click (Go to Definition) to jump straight into windUniforms.glsl — the cross-module navigation that stock GLSL tooling can't do. Hover/jump also work for top-level uniform/in/out declarations and function definitions; hovering a built-in — deck's project_position_to_clipspace or core GLSL like clamp/texture/mix — shows its signature, and cmd-clicking a deck builtin jumps into the real deck source in node_modules.
Type wind. for member completion (the whole uniform block), and open the Outline view (or breadcrumbs) for the file's document symbols — its uniforms, functions, and any blocks declared in it.
