@coldsmirk/inkstone-core 0.19.2 → 0.20.1

package/README.md

@@ -7,7 +7,7 @@ Part of [inkstone](https://github.com/coldsmirk/inkstone). The editor layers ([`
 ## What you get
 
 - **`getHighlighter()`** — the process-wide `HighlighterCore` promise. JavaScript / TypeScript / JSON / SQL grammars and the catppuccin theme pair load by default.
-- **`configureHighlighter(config)`** — extend or replace the default grammar / theme set, once, before any editor mounts. `DEFAULT_HIGHLIGHTER_LANGS` is exported so extension is additive.
+- **`configureHighlighter(config)`** — extend or replace the default grammar / theme set, and choose the regex engine (`engine`: the strict JavaScript engine by default; `createJavaScriptRegexEngine({ forgiving: true })` for grammars the strict one refuses, or the Oniguruma WASM engine), once, before any editor mounts. `DEFAULT_HIGHLIGHTER_LANGS` is exported so extension is additive.
 - **`shikiThemeId(dark)`** plus the `INKSTONE_LIGHT_THEME` / `INKSTONE_DARK_THEME` constants — the theme names to pass wherever a Shiki theme id is expected.
 - **`configureEditorSurface(surfaces)`** — re-light the editors' own surfaces in your design language, once, before any editor mounts: per-scheme CSS color literals for `background` (content and gutter), `lineHighlight`, `lineNumber`, `widget` (completion, hover, parameter hints, the find widget and search panels), `widgetBorder`, and `widgetSelection`. The catppuccin pair keeps its syntax palette and gets these baked into its theme colors — Monaco, static rendering, and CodeMirror's chrome all read the same values — so an editor sits inside the app instead of bringing a second dark. A role or scheme left out keeps the flavor's own color, a later call replaces the schemes it names, and values must be hex colors (`#rrggbb`, `#rrggbbaa`) — Monaco parses theme colors as hex and paints red for anything else, so a `var()` reference or an `rgb(…)` is refused up front. Keep `lineHighlight` translucent: CodeMirror draws selections behind the content, so an opaque active line would hide them. `getEditorSurface(dark)` reads what was configured.
 - **`CODE_FONT_FAMILY`** — the shared code font stack both editor engines render with: the page's `--inkstone-font-family-code` CSS token when defined, else the platform's native monospace.

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-import { HighlighterCore, HighlighterCore as HighlighterCore$1, LanguageInput, ThemeInput, ThemeRegistration } from "shiki/core";
+import { HighlighterCore, HighlighterCore as HighlighterCore$1, LanguageInput, RegexEngine, ThemeInput, ThemeRegistration } from "shiki/core";
 //#region src/code-font.d.ts
 /**
  * The code font stack every inkstone editor host renders with: the page's
@@ -109,6 +109,13 @@ interface HighlighterConfig {
    * the editor components select it by id).
    */
   themes?: ThemeInput[];
+  /**
+   * The regex engine the highlighter tokenizes with, replacing the default JavaScript engine
+   * in its strict form — for an app that loads grammars the strict engine refuses
+   * (`createJavaScriptRegexEngine({ forgiving: true })`), or one that ships the Oniguruma
+   * WASM and wants every grammar exact.
+   */
+  engine?: RegexEngine;
 }
 /**
  * Configure the shared highlighter before its first use. The highlighter is a process-wide

package/dist/index.js

@@ -129,7 +129,7 @@ function getHighlighter() {
 			...registry.config.themes ?? []
 		],
 		langs: registry.config.langs ?? [...DEFAULT_HIGHLIGHTER_LANGS],
-		engine: createJavaScriptRegexEngine()
+		engine: registry.config.engine ?? createJavaScriptRegexEngine()
 	});
 	registry.promise = attempt;
 	attempt.catch(() => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coldsmirk/inkstone-core",
-  "version": "0.19.2",
+  "version": "0.20.1",
   "description": "Shared Shiki highlighter service for the inkstone editor toolkit: one fine-grained singleton (catppuccin themes, JS regex engine) reused by Monaco, static rendering, and markdown surfaces.",
   "keywords": [
     "shiki",