@gluonjs/language-server

The Gluon language server analyzes imported html, svg, css, and aliased compose(Component, props) tagged templates without evaluating application code. The public service and the gluon-template-check CI command share the same two-pass project analyzer.

analyzeStaticGluonProject() and gluon-project-analyze expose the broader versioned project report. It inventories source files, component shapes, public Custom Element contracts, templates and bindings, constructable style dependencies, literal routes and stores, SSR/hydration API boundaries, and the same diagnostics used by the editor. Every evidence record is marked exact, structural, or indeterminate; the analyzer never imports application code.

Diagnostics cover unknown Custom Elements, declared Custom Element properties, events, and named light-DOM slots, ARIA names, invalid binding positions, void-element children, and inline style elements. defineElement() declarations expose tag definitions, static properties, events, and slots metadata to completion, hover, definition, and workspace rename operations. Literal @customElement() declarations expose the same tag definition; @property() fields join the public property list while @state() remains internal. Aliased decorator imports are recognized. Literal defineGluonElement() definitions expose the same inferred tag, property, event, and slot contract and share the compiler's tag/setup ownership diagnostics. Unknown literal named light-DOM assignments receive GLUON_TEMPLATE_SLOT_UNKNOWN at the slot-name source range. declarationsFromCustomElementsManifest() accepts standard manifest module declarations and exposes their fields, events, and slots to the same analyzer. Every emitted code is required to exist in the public @gluonjs/compiler diagnostic catalog shared with the Playground and Devtools reference.

Agent-facing contracts are available through getGluonApiManifest() and the generated docs/api-manifest.json. The gluon-check alias accepts --json and emits a versioned result containing the public API manifest, checked files, stable diagnostics, and an ok flag:

@gluonjs/language-server at a glance

Runtime: node · Release: 1.13.0

Documentation guide · npm · Source

Public API: @gluonjs/language-server

Install

npm install @gluonjs/language-server

Quick start

gluon-language-server
# or
 gluon-project-analyze .

Choose this package when

• Static analysis for imported templates and alias-aware tagged templates.
• Language server, project analyzer, and CI template checks.
• Diagnostics without evaluating application code.

Choose another boundary when:

• Does not execute project code or modify source files.
• Reports evidence records rather than browser behavior.

Related documentation

• Tooling
• Quality

gluon-check --json src > gluon-check.json
node scripts/build-api-manifest.mjs --check

The JSON path is additive; gluon-template-check keeps its existing human output and exit codes.

gluon-template-check src
gluon-project-analyze src > project-analysis.json
gluon-language-server --stdio

The LSP uses standard Content-Length framing, reports the lockstep package version through initialize.serverInfo, and supports full-document sync, diagnostics, completion, hover, go-to-definition, references, rename, and semantic tokens. .gluon documents use the compiler's typed SFC block parser; template and script ranges remain in the original file and malformed documents are isolated. Compiler-backed parsing preserves component, props, layer, style ID, default-import, and default-slot block metadata. Editor symbol operations link literal defineElement() declarations, the template component attribute, relative default .gluon imports, and static template/CSS class names across the same open workspace with original-source ranges. Relative import navigation is intentionally open-document based, and rename changes local component aliases rather than filenames. The server does not replace TypeScript or CSS language services; arbitrary expressions, preprocessors, package imports, dynamic imports, and filesystem rename remain outside the contract. Protocol behavior is tested through GluonProtocolServer without VS Code. The maintained VS Code client is in editors/vscode and starts the lockstep server from the workspace or extension configuration.

gluon-mcp is a read-only MCP stdio server backed by the same API manifest and diagnostic catalog. It exposes get_api_manifest, explain_error, and validate_code tools; it does not execute project code or modify files.

License

MIT License, Copyright © 2026 Marc Malerei.