Presolve/Docs
Menu

These docs cover 0.2.0-beta.26. Each guide distinguishes supported beta behavior, explicit deployment boundaries, and retained 0.1 compatibility material.

Browse documentationAll guides
DocumentationChoose a guide or reference

Reference · developer tooling

VS Code

The Presolve extension connects VS Code to the compiler installed in your application. It adds framework-specific diagnostics and explanation without replacing the TypeScript server or maintaining a second TSX analyzer.

Install

code --install-extension fierstdev.presolve-vscode

Open the project root created by pnpm create presolve, then run pnpm install. The extension resolves node_modules/.bin/presolve from that workspace, so editor results use the same release train as checks and builds.

Compiler diagnostics

On save, the extension asks the project-local compiler to check the active TypeScript or TSX file and publishes its exact diagnostic code, message, severity, and source range into VS Code’s Problems view.

TypeScriptThe workspace TypeScript server owns normal type, import, and language diagnostics.
PresolveThe installed compiler owns components, state, actions, effects, structure, ownership, serialization, and capabilities.

Disable automatic checks with presolve.checkOnSave, or opt into checks when a file opens with presolve.checkOnOpen.

Compiler-derived CodeLens

Each compiler-recognized component gets a Presolve component · Explain lens. It comes from presolve explain, so a class that merely resembles a component does not acquire framework identity.

Presolve component · Explainexport class Counter extends Component { … }

Select the lens or run Presolve: Explain Active File to open the compiler’s JSON explanation beside the source. The result includes source size, component classes, routes, class declarations, render methods, and source diagnostics.

Commands

CommandPurpose
Show Workspace StatusOpen a quick action menu and show installed release status.
Check WorkspaceRun the canonical application check and reveal compiler output.
Check Active FileRefresh exact Presolve diagnostics for the current source.
Explain Active FileOpen compiler-owned source facts as formatted JSON.
Build Production PublicationRun the project-local production build.
Run DoctorInspect the installed toolchain and project environment.
Open DocumentationOpen the current Presolve guides.

Status bar

The status item distinguishes disabled, unconfigured, checking, failing, and clean states. Select it to access the most common compiler commands without leaving the editor.

Configuration

presolve.enable

Enable all extension workspace integration. Default: true.

presolve.checkOnSave

Run compiler diagnostics after saving a Presolve source. Default: true.

presolve.checkOnOpen

Check source immediately when it opens. Default: false.

presolve.codeLens

Show compiler-derived component explanation lenses. Default: true.

Troubleshooting

  1. Open the repository folderA loose TSX file has no project-local compiler or configuration authority.
  2. Install dependenciesConfirm node_modules/.bin/presolve exists.
  3. Use the scaffolded TypeScriptKeep the supported version and generated tsconfig.json.
  4. Run DoctorInspect the exact project environment from the command palette.
  5. Compare the terminalpnpm check remains the canonical workspace-wide release gate.
One semantic authority

The extension never parses emitted JavaScript, suppresses TypeScript errors, or fabricates component identities. Hover, definition, reference, and symbol expansion beyond native TypeScript will be added only through versioned compiler query products.