ProseLint Web v1.0.1: Updated Vale Engine, Class Filtering, Comment Delimiters, and Org Mode

ProseLint Web v1.0.1 is now available with an updated Vale engine, two new filtering features in the Formats tab, and native Org Mode support.

This release focuses on giving you finer control over what Vale lints and expanding format coverage — all still running entirely in your browser.

What's new in v1.0.1

1) Updated Vale engine (v3.14.1) with critical bug fix

The underlying Vale WASM engine has been updated to v3.14.1, which fixes a bug where scope filtering settings could leak across linting sessions.

In the previous engine, configuring SkippedScopes or IgnoredClasses would permanently alter the defaults for all subsequent linting calls — even after reinitializing. This happened because the WASM runtime is long-lived (unlike the CLI, which starts fresh each run). The fix ensures scope state is initialized cleanly on every lint.

If you previously noticed scope filtering behaving inconsistently after changing settings, this update resolves it.

We also improved how ProseLint Web detects engine updates. The WASM version is now read automatically from a version file deployed alongside the binary. Future engine updates will take effect immediately — no code changes needed, and your browser cache will invalidate itself when a new version is detected.

2) Class filtering for HTML content

You can now tell Vale to ignore content inside HTML elements by their CSS class name.

Open the Formats tab and scroll to the new Class Filtering section. You'll find presets for common class names:

.highlight — Syntax-highlighted code blocks
.code-block — Generic code block containers
.no-lint — Explicitly excluded from linting
.math — Mathematical formula blocks
.katex — KaTeX math rendering containers
.mermaid — Mermaid diagram blocks

Toggle any preset on, or type a custom class name to add your own.

What this means for you:

Stop getting false positives from code examples, math notation, or diagram markup embedded in your HTML or Markdown
Add project-specific class names (like .api-response or .changelog-entry) without editing any config files
Works alongside existing scope filtering — combine tag-level and class-level exclusions for precise control

3) Comment delimiters for linting code comments

A new Comment Delimiters section in the Formats tab lets you tell Vale how to extract prose from source code comments.

Enable a preset and Vale will understand how to find and lint the text inside comments for that language:

Python — # ...
C / C++ (block) — /* ... */
Lua — -- ...
Ruby — # ...
R — # ...

What this means for you:

Lint the prose quality of your code comments and docstrings directly in the browser
Catch style guide violations, spelling errors, and readability issues in comments that users and contributors actually read
Useful for API documentation maintained as inline comments

4) Native Org Mode support

ProseLint Web now lints .org files natively instead of falling back to plain text. This means Vale understands Org Mode's document structure — headings, blocks, markup — and can apply rules with correct position mapping.

Previously, Org files were treated as plain text, which meant structural elements like #+BEGIN_SRC blocks would generate false positives. Now they're handled correctly.

All changes at a glance

Feature	Before	After
Vale engine	Older build	v3.14.1 with scope leak fix
Class filtering	Not available	6 presets + custom classes
Comment delimiters	Not available	5 language presets
Org Mode linting	Plain text fallback	Native `.org` support
WASM version detection	Hardcoded, manual bumps	Automatic from version file

Start using ProseLint Web v1.0.1 now

Head to the editor, open the Packages modal, and check out the Formats tab to try class filtering and comment delimiters.

If you had cached the previous WASM engine, your browser will automatically detect the new version and fetch the updated binary on your next visit.

Try ProseLint Web free — no data leaves your browser. Lint Markdown, HTML, MDX, AsciiDoc, Org Mode, and plain text entirely client-side.