Manifold Language Server

A Language Server Protocol (LSP) implementation for the Manifold HTML framework, providing intelligent code completion, syntax highlighting, and error checking for Manifold's reactive HTML syntax.

Features

Syntax Highlighting: Proper color coding for Manifold directives and interpolations
Code Completion: Intelligent completions for Manifold directives, HTML elements, and attributes
Scoped Suggestions: Automatic completions for ${} interpolations, Manifold attributes, and property access with a toggleable auto-trigger command (Manifold: Toggle Auto Suggestions)
Type Hints: Type information for variables and expressions
Error Detection: Real-time error reporting for invalid Manifold syntax
Go-to Definition: Navigate to variable and function definitions
Hover Information: Contextual information for Manifold elements

JetBrains IDE support

A Gradle-based IntelliJ Platform plugin lives under jetbrains/. Use ./gradlew runIde from that directory to launch a sandbox IDE, or ./gradlew buildPlugin to produce an installable ZIP. The plugin looks for the manifold-language-server binary in jetbrains/bin/<platform>/, the Cargo target folders, MANIFOLD_LSP_BIN, or your PATH.

Manifold Syntax Support

This language server supports the following Manifold features:

Directives

:if, :else, :elif - Conditional rendering
:each - List iteration
:value, :checked - One-way data binding
:sync:value, :sync:checked - Two-way data binding
:onclick, :onchange, etc. - Event handlers
:class, :style - Dynamic styling

Data Attributes

data-mf-register - Register a Manifold context
data-mf-ignore - Exclude elements from Manifold processing

Text Interpolation

${} expressions for dynamic text content
Variable references and expressions within interpolations

Example Manifold HTML

<!DOCTYPE html>
<html lang="en">
	<body data-mf-register>
		<h1>Todo App</h1>

		<div>
			<input :sync:value="newTodo" placeholder="Add a todo..." />
			<button :onclick="addTodo()">Add</button>
		</div>

		<ul>
			<li :each="todos as todo, index">
				<span :class="{ completed: todo.done }">${todo.text}</span>
				<button :onclick="toggleTodo(index)">Toggle</button>
				<button :onclick="deleteTodo(index)">Delete</button>
			</li>
		</ul>

		<p :if="todos.length === 0">No todos yet!</p>
		<p :else>Total: ${todos.length} todos</p>
	</body>
</html>

Other Editors

The language server speaks standard LSP, so you can wire it into editors beyond VS Code and JetBrains.

Vim / Neovim

Install the language server binary (cargo install --path . or copy target/release/manifold-language-server onto your PATH).

Add an LSP client configuration. For Neovim with nvim-lspconfig:

```lua
require('lspconfig').manifold_html.setup {

cmd = { 'manifold-language-server' }, filetypes = { 'html', 'javascript', 'typescript' }, root_dir = require('lspconfig.util').find_git_ancestor, }


    For Vim with [`coc.nvim`](https://github.com/neoclide/coc.nvim), add to `coc-settings.json`:

    ```json
    {

"languageserver": {
"manifold": {
"command": "manifold-language-server",
"filetypes": ["html", "javascript", "typescript"],
"rootPatterns": [".git"]
}
}
}

Restart the editor. Opening a Manifold HTML file should now trigger completions, diagnostics, and hovers.

The root_dir/rootPatterns entries tell your LSP client how to decide where a project boundary lives. Pointing them at .git is usually enough; feel free to remove the setting if your editor already scopes workspaces the way you expect.

Helix

Ensure manifold-language-server is on your PATH (or provide an absolute path in the command below).

Add the following block to your ~/.config/helix/languages.toml:

```toml
[[language]]
name = "html"
scope = "text.html.basic"
file-types = ["html", "htm"]

[language.language-server]
command = "manifold-language-server"
args = []

[[language.auto-pairs]]
open = "${"
close = "}"
```

Restart Helix. The server will attach to HTML buffers and provide Manifold-specific assistance.

Publishing

VS Code Marketplace

Generate a Personal Access Token with “Marketplace → Manage” scope and store it as the VSCE_TOKEN GitHub secret.
Pushing changes to the release branch automatically runs the “Build and Publish VS Code Extension” workflow. The pipeline checks that Cargo.toml’s version increased compared to the previous revision; if so, it builds, tests, packages, and publishes the .vsix. You can still publish by cutting a tag, releasing in GitHub, or triggering the workflow manually.
When the secret is missing, the workflow still produces the .vsix artifact, leaving marketplace upload for a manual run.

JetBrains Marketplace

Create a JetBrains Marketplace permanent token in the Vendor Portal and add it to the repository secrets as JETBRAINS_MARKETPLACE_TOKEN.
Pushing to the release branch kicks off the “Build and Publish JetBrains Plugin” workflow. Like the VS Code pipeline, it only proceeds when the version in Cargo.toml moves forward, then builds the Rust server in release mode, packages the plugin ZIP, uploads it as an artifact, and publishes when the secret is present.
If the token is absent, the job still produces the ZIP so you can upload it manually through the vendor portal.

VS Code Extension Details

Level up your Manifold HTML authoring with completions, diagnostics, inline type hints, and more—directly inside VS Code.

Features

Context-aware completions for Manifold directives, loop locals, and state properties
Inline type annotations to understand what each expression returns
Diagnostics that highlight unsupported syntax or missing variables as you type
Go to Definition and Find References across Manifold states and templates
Custom commands for toggling auto-triggered completions and type hints

Getting Started

Install the Manifold Language Client from the VS Code Marketplace.
Open a project containing Manifold HTML templates.
The extension activates automatically for HTML/JavaScript/TypeScript files. Toggle auto-completions or inline hints via the command palette (⌘⇧P / Ctrl+Shift+P).

Commands

Command	Description
`Manifold: Toggle Auto Suggestions`	Enable or disable automatic completions when typing attribute expressions.
`Manifold: Toggle Type Annotations`	Show or hide inline type hints for expressions.
`Manifold: Restart Language Server`	Manually restart the bundled Manifold language server process.

Configuration

Settings → Manifold Language Server

Setting	Default	Notes
`manifoldLanguageServer.completions.autoTrigger`	`true`	Automatically request completions after triggering characters.
`manifoldLanguageServer.typeHints.enabled`	`true`	Show inline type annotations when available.
`manifoldLanguageServer.trace.server`	`off`	Enables verbose logging between VS Code and the LSP for troubleshooting.
`manifoldLanguageServer.documentSelectors`	`html`, `javascript`, `typescript`	Customize which language IDs should activate the server.

Manifold Language Client

Jacob Runge

Manifold Language Server

Features

JetBrains IDE support

Manifold Syntax Support

Directives

Data Attributes

Text Interpolation

Example Manifold HTML

Other Editors

Vim / Neovim

Helix

Publishing

VS Code Marketplace

JetBrains Marketplace

VS Code Extension Details

Features

Getting Started

Commands

Configuration