@hyperfixi/vite-plugin 3.3.0 → 4.0.0

package/dist/index.d.cts

@@ -1,5 +1,4 @@
 import { Plugin } from 'vite';
-import { ASTNode } from '@hyperfixi/core/parser/hybrid/ast-types';
 
 /**
  * Vite Plugin Types
@@ -11,19 +10,9 @@ import { ASTNode } from '@hyperfixi/core/parser/hybrid/ast-types';
  */
 interface HyperfixiPluginOptions {
     /**
-     * Bundle generation mode:
-     * - 'interpret': Generate minimal bundle with parser (default, ~8KB gzip)
-     * - 'compile': Pre-compile hyperscript to JS at build time (~500 bytes gzip)
-     *
-     * Compile mode limitations:
-     * - No dynamic hyperscript (runtime execute() won't work)
-     * - No block commands (if, for, repeat, while, fetch)
-     * - HTML must be transformed to use data-h attributes
-     *
-     * Use compile mode when:
-     * - Bundle size is critical (<1KB target)
-     * - All hyperscript is static (no dynamic generation)
-     * - Only simple commands are used (toggle, add, remove, set, etc.)
+     * @deprecated Removed in 4.0. `'compile'` pre-compiled handlers to JS with
+     * `@hyperfixi/core`'s parser; it went with that parser, and the plugin always emits the
+     * engine-module bundle now (setting `'compile'` logs a warning and does that).
      */
     mode?: 'interpret' | 'compile';
     /**
@@ -51,16 +40,19 @@ interface HyperfixiPluginOptions {
      */
     positional?: boolean;
     /**
-     * Enable HTMX integration (auto-process after htmx:afterSettle).
+     * Hand content htmx swaps in to the engine (`htmx:load` / `htmx:afterSettle`
+     * → `processNode`). On by default when the scan finds htmx attributes.
+     * htmx itself is not bundled: load htmx 4 beside the generated bundle.
      */
     htmx?: boolean;
     /**
      * Development mode fallback strategy.
-     * - 'hybrid-complete': Use pre-built hybrid-complete bundle for faster dev (default)
-     * - 'full': Use full bundle for complete compatibility
-     * - 'auto': Generate minimal bundle even in dev
+     * - 'everything': the engine with every module (34 KB gzipped), for faster dev rebuilds
+     * - 'auto': generate the module-list bundle in dev too
+     * - 'hybrid-complete' | 'full': accepted for compatibility; both mean 'everything'
+     *   (core's prebuilt bundles are no longer what the plugin falls back to)
      */
-    devFallback?: 'hybrid-complete' | 'full' | 'auto';
+    devFallback?: 'everything' | 'hybrid-complete' | 'full' | 'auto';
     /**
      * Global variable name for the hyperfixi API.
      * Defaults to 'hyperfixi'.
@@ -215,26 +207,26 @@ interface HtmxUsage {
      */
     needsSwapTiming?: boolean;
     /**
-     * htmx v4 reactive/streaming surface detected. Each flag pulls in the
-     * corresponding bundle module; collectively they're what makes
-     * `hyperfixi-hx-v4.js` the right premade choice when none would do.
+     * htmx v4 reactive/streaming surface detected. `needsHxLive` pulls in the
+     * engine's reactivity modules; htmx itself is not bundled (core's
+     * hyperfixi-hx-v4.js, the premade bundle for this surface, retired in C3).
      *
      * Optional to keep older fixture literals (and callers that ignore
      * htmx v4) compatible. Scanner code always emits explicit `false`.
      */
     needsHxLive?: boolean;
-    /** sse-connect / sse-swap detected. Pulls in `@hyperfixi/core/htmx/sse`. */
+    /** sse-connect / sse-swap detected. Detection only: SSE is htmx 4's (core's htmx layer retired in C3). */
     needsSSE?: boolean;
-    /** ws-connect / ws-send detected. Pulls in `@hyperfixi/core/htmx/ws`. */
+    /** ws-connect / ws-send detected. Detection only: WebSockets are htmx 4's. */
     needsWS?: boolean;
     /**
      * `bind $x to <expr>.<prop>` detected inside an `_=` attribute. Implies
-     * reactivity (the bind feature lives in `@hyperfixi/reactivity`).
+     * reactivity (the engine's reactivity modules).
      */
     needsBindToProperty?: boolean;
     /**
-     * Any hx-v4-class feature → vite-generated bundle should auto-install
-     * `@hyperfixi/reactivity`. Derived from needsHxLive || needsBindToProperty.
+     * Any reactive feature → the generated bundle registers the engine's
+     * reactivity modules. Derived from needsHxLive || needsBindToProperty.
      */
     needsReactivity?: boolean;
 }
@@ -254,9 +246,9 @@ interface FileUsage {
     htmx?: HtmxUsage;
     /**
      * Reactivity-requiring constructs detected directly inside `_=` script
-     * bodies (independent of htmx attributes). Today: `bind` features
-     * (`live`/`when`/`bind`/`^var`). When true, the generated bundle should
-     * auto-install `@hyperfixi/reactivity`.
+     * bodies (independent of htmx attributes): the engine's `live` / `when` /
+     * `bind` features and the `^var` form. When true, the generated bundle
+     * registers the engine's `reactivity` (and `liveTemplates`) modules.
      *
      * Kept top-level rather than under `htmx` because authors may use these
      * features without any htmx attributes at all (pure `_=` reactive code).
@@ -272,6 +264,10 @@ interface FileUsage {
      * in an `_=` body. Implies `needsReactivity` too.
      */
     needsBindToProperty?: boolean;
+    /** `new X(…)` seen: the engine's `construct` addition is registered. */
+    needsConstruct?: boolean;
+    /** `cookies` seen: the engine's `cookies` expression module is registered. */
+    needsCookies?: boolean;
 }
 /**
  * Aggregated usage information across all files
@@ -290,7 +286,7 @@ interface AggregatedUsage {
     /**
      * Whether any file uses reactivity-requiring constructs (either via
      * `hx-live` attributes or inside `_=` scripts). Drives the generated
-     * bundle's auto-install of `@hyperfixi/reactivity`.
+     * bundle's registration of the engine's reactivity modules.
      *
      * Optional to keep test fixtures compatible; the aggregator always
      * emits an explicit boolean.
@@ -298,6 +294,10 @@ interface AggregatedUsage {
     needsReactivity?: boolean;
     /** Whether any file uses explicit-property bind. */
     needsBindToProperty?: boolean;
+    /** Whether any file uses `new X(…)` (the engine's `construct` addition). */
+    needsConstruct?: boolean;
+    /** Whether any file reads `cookies`. */
+    needsCookies?: boolean;
     /** Map of file paths to their usage */
     fileUsage: Map<string, FileUsage>;
 }
@@ -438,92 +438,6 @@ declare class DomainAggregator {
     private isEqual;
 }
 
-/**
- * Compiler
- *
- * Compiles hyperscript AST to JavaScript at build time.
- * Eliminates the need for runtime parsing.
- *
- * Multilingual support:
- * - For English: Uses HybridParser directly
- * - For other languages: Uses semantic parser to translate → AST → JavaScript
- * - Semantic parsing happens at BUILD time (zero runtime overhead)
- */
-
-/**
- * Result shape returned by the semantic parse function.
- * Matches `ParseWithConfidenceResult` from `@lokascript/semantic`.
- */
-interface SemanticParseResult {
-    confidence: number;
-    node?: unknown;
-    error?: string | undefined;
-}
-/**
- * Function that parses input in a given language and returns a confidence
- * score plus an optional semantic node. Matches `parseSemantic` / `parseWithConfidence`
- * from `@lokascript/semantic`.
- */
-type SemanticParseFn = (input: string, language: string) => SemanticParseResult;
-/**
- * Function that checks whether a language is registered for parsing.
- * Matches `isLanguageRegistered` from `@lokascript/semantic`.
- */
-type SupportsLanguageFn = (language: string) => boolean;
-type BuildASTFn = (node: unknown) => {
-    ast: ASTNode;
-    warnings: string[];
-};
-/**
- * Configure the semantic parser for multilingual compilation.
- *
- * @example
- * ```typescript
- * import { parseSemantic, isLanguageRegistered, buildAST } from '@lokascript/semantic';
- * import { setSemanticParser } from '@hyperfixi/vite-plugin';
- *
- * setSemanticParser(parseSemantic, isLanguageRegistered, buildAST);
- * ```
- */
-declare function setSemanticParser(parse: SemanticParseFn, supports: SupportsLanguageFn, buildAST: BuildASTFn): void;
-/**
- * Clear the semantic parser (for testing).
- */
-declare function clearSemanticParser(): void;
-/**
- * Check if semantic parser is available.
- */
-declare function hasSemanticParser(): boolean;
-interface CompiledHandler {
-    /** Unique handler ID (h0, h1, etc.) */
-    id: string;
-    /** Event name (click, input, etc.) */
-    event: string;
-    /** Event modifiers */
-    modifiers: {
-        prevent?: boolean;
-        stop?: boolean;
-        once?: boolean;
-        debounce?: number;
-        throttle?: number;
-    };
-    /** Compiled JavaScript code */
-    code: string;
-    /** Whether handler needs the mini-evaluator for dynamic expressions */
-    needsEvaluator: boolean;
-    /** Original hyperscript for debugging */
-    original: string;
-}
-/**
- * Compile options for multilingual support.
- */
-interface CompileOptions {
-    /** Language code (ISO 639-1). Defaults to 'en'. */
-    language?: string;
-    /** Enable debug logging. */
-    debug?: boolean;
-}
-
 /**
  * Language Keywords for Detection
  *
@@ -620,24 +534,16 @@ declare function getOptimalRegion(languages: Set<SupportedLanguage>): 'western'
  * })
  * ```
  *
- * @example
- * ```javascript
- * // Compile mode for smallest bundles (~500 bytes)
- * hyperfixi({
- *   mode: 'compile',  // Pre-compile hyperscript to JS
- *   debug: true,
- * })
- * ```
  */
 
 /**
  * Compute a hash of the current usage for dev-server cache invalidation.
  *
  * Every input that influences bundle SELECTION must be part of this hash.
- * The htmx/reactivity flags route to the hybrid-hx / hx-v4 tiers; before they
- * were hashed, adding or removing an hx-live/sse-connect/ws-send attribute —
- * without touching any command/block/language — left the cached dev bundle at
- * the wrong tier. Exported for tests.
+ * The htmx/reactivity flags decide which engine modules are registered; before
+ * they were hashed, adding or removing an hx-live/sse-connect/ws-send
+ * attribute — without touching any command/block/language — left the cached
+ * dev bundle stale. Exported for tests.
  */
 declare function computeUsageHash(usage: AggregatedUsage): string;
 /**
@@ -648,4 +554,4 @@ declare function computeUsageHash(usage: AggregatedUsage): string;
  */
 declare function hyperfixi(options?: HyperfixiPluginOptions): Plugin;
 
-export { type AggregatedUsage, type CompileOptions, type CompiledHandler, type CustomLanguageKeywords, type DomainAggregatedUsage, DomainAggregator, type DomainFileUsage, type DomainScanRule, DomainScanner, type FileUsage, type HyperfixiPluginOptions, REGIONS, SUPPORTED_LANGUAGES, type ServerBridgeOptions, type SupportedLanguage, clearCustomKeywords, clearSemanticParser, computeUsageHash, hyperfixi as default, descriptorToScanRule, detectLanguages, getAllLanguageCodes, getKeywordsForLanguage, getOptimalRegion, hasSemanticParser, hyperfixi, isNonLatinLanguage, registerCustomKeywords, setSemanticParser };
+export { type AggregatedUsage, type CustomLanguageKeywords, type DomainAggregatedUsage, DomainAggregator, type DomainFileUsage, type DomainScanRule, DomainScanner, type FileUsage, type HyperfixiPluginOptions, REGIONS, SUPPORTED_LANGUAGES, type ServerBridgeOptions, type SupportedLanguage, clearCustomKeywords, computeUsageHash, hyperfixi as default, descriptorToScanRule, detectLanguages, getAllLanguageCodes, getKeywordsForLanguage, getOptimalRegion, hyperfixi, isNonLatinLanguage, registerCustomKeywords };

package/dist/index.d.ts

@@ -1,5 +1,4 @@
 import { Plugin } from 'vite';
-import { ASTNode } from '@hyperfixi/core/parser/hybrid/ast-types';
 
 /**
  * Vite Plugin Types
@@ -11,19 +10,9 @@ import { ASTNode } from '@hyperfixi/core/parser/hybrid/ast-types';
  */
 interface HyperfixiPluginOptions {
     /**
-     * Bundle generation mode:
-     * - 'interpret': Generate minimal bundle with parser (default, ~8KB gzip)
-     * - 'compile': Pre-compile hyperscript to JS at build time (~500 bytes gzip)
-     *
-     * Compile mode limitations:
-     * - No dynamic hyperscript (runtime execute() won't work)
-     * - No block commands (if, for, repeat, while, fetch)
-     * - HTML must be transformed to use data-h attributes
-     *
-     * Use compile mode when:
-     * - Bundle size is critical (<1KB target)
-     * - All hyperscript is static (no dynamic generation)
-     * - Only simple commands are used (toggle, add, remove, set, etc.)
+     * @deprecated Removed in 4.0. `'compile'` pre-compiled handlers to JS with
+     * `@hyperfixi/core`'s parser; it went with that parser, and the plugin always emits the
+     * engine-module bundle now (setting `'compile'` logs a warning and does that).
      */
     mode?: 'interpret' | 'compile';
     /**
@@ -51,16 +40,19 @@ interface HyperfixiPluginOptions {
      */
     positional?: boolean;
     /**
-     * Enable HTMX integration (auto-process after htmx:afterSettle).
+     * Hand content htmx swaps in to the engine (`htmx:load` / `htmx:afterSettle`
+     * → `processNode`). On by default when the scan finds htmx attributes.
+     * htmx itself is not bundled: load htmx 4 beside the generated bundle.
      */
     htmx?: boolean;
     /**
      * Development mode fallback strategy.
-     * - 'hybrid-complete': Use pre-built hybrid-complete bundle for faster dev (default)
-     * - 'full': Use full bundle for complete compatibility
-     * - 'auto': Generate minimal bundle even in dev
+     * - 'everything': the engine with every module (34 KB gzipped), for faster dev rebuilds
+     * - 'auto': generate the module-list bundle in dev too
+     * - 'hybrid-complete' | 'full': accepted for compatibility; both mean 'everything'
+     *   (core's prebuilt bundles are no longer what the plugin falls back to)
      */
-    devFallback?: 'hybrid-complete' | 'full' | 'auto';
+    devFallback?: 'everything' | 'hybrid-complete' | 'full' | 'auto';
     /**
      * Global variable name for the hyperfixi API.
      * Defaults to 'hyperfixi'.
@@ -215,26 +207,26 @@ interface HtmxUsage {
      */
     needsSwapTiming?: boolean;
     /**
-     * htmx v4 reactive/streaming surface detected. Each flag pulls in the
-     * corresponding bundle module; collectively they're what makes
-     * `hyperfixi-hx-v4.js` the right premade choice when none would do.
+     * htmx v4 reactive/streaming surface detected. `needsHxLive` pulls in the
+     * engine's reactivity modules; htmx itself is not bundled (core's
+     * hyperfixi-hx-v4.js, the premade bundle for this surface, retired in C3).
      *
      * Optional to keep older fixture literals (and callers that ignore
      * htmx v4) compatible. Scanner code always emits explicit `false`.
      */
     needsHxLive?: boolean;
-    /** sse-connect / sse-swap detected. Pulls in `@hyperfixi/core/htmx/sse`. */
+    /** sse-connect / sse-swap detected. Detection only: SSE is htmx 4's (core's htmx layer retired in C3). */
     needsSSE?: boolean;
-    /** ws-connect / ws-send detected. Pulls in `@hyperfixi/core/htmx/ws`. */
+    /** ws-connect / ws-send detected. Detection only: WebSockets are htmx 4's. */
     needsWS?: boolean;
     /**
      * `bind $x to <expr>.<prop>` detected inside an `_=` attribute. Implies
-     * reactivity (the bind feature lives in `@hyperfixi/reactivity`).
+     * reactivity (the engine's reactivity modules).
      */
     needsBindToProperty?: boolean;
     /**
-     * Any hx-v4-class feature → vite-generated bundle should auto-install
-     * `@hyperfixi/reactivity`. Derived from needsHxLive || needsBindToProperty.
+     * Any reactive feature → the generated bundle registers the engine's
+     * reactivity modules. Derived from needsHxLive || needsBindToProperty.
      */
     needsReactivity?: boolean;
 }
@@ -254,9 +246,9 @@ interface FileUsage {
     htmx?: HtmxUsage;
     /**
      * Reactivity-requiring constructs detected directly inside `_=` script
-     * bodies (independent of htmx attributes). Today: `bind` features
-     * (`live`/`when`/`bind`/`^var`). When true, the generated bundle should
-     * auto-install `@hyperfixi/reactivity`.
+     * bodies (independent of htmx attributes): the engine's `live` / `when` /
+     * `bind` features and the `^var` form. When true, the generated bundle
+     * registers the engine's `reactivity` (and `liveTemplates`) modules.
      *
      * Kept top-level rather than under `htmx` because authors may use these
      * features without any htmx attributes at all (pure `_=` reactive code).
@@ -272,6 +264,10 @@ interface FileUsage {
      * in an `_=` body. Implies `needsReactivity` too.
      */
     needsBindToProperty?: boolean;
+    /** `new X(…)` seen: the engine's `construct` addition is registered. */
+    needsConstruct?: boolean;
+    /** `cookies` seen: the engine's `cookies` expression module is registered. */
+    needsCookies?: boolean;
 }
 /**
  * Aggregated usage information across all files
@@ -290,7 +286,7 @@ interface AggregatedUsage {
     /**
      * Whether any file uses reactivity-requiring constructs (either via
      * `hx-live` attributes or inside `_=` scripts). Drives the generated
-     * bundle's auto-install of `@hyperfixi/reactivity`.
+     * bundle's registration of the engine's reactivity modules.
      *
      * Optional to keep test fixtures compatible; the aggregator always
      * emits an explicit boolean.
@@ -298,6 +294,10 @@ interface AggregatedUsage {
     needsReactivity?: boolean;
     /** Whether any file uses explicit-property bind. */
     needsBindToProperty?: boolean;
+    /** Whether any file uses `new X(…)` (the engine's `construct` addition). */
+    needsConstruct?: boolean;
+    /** Whether any file reads `cookies`. */
+    needsCookies?: boolean;
     /** Map of file paths to their usage */
     fileUsage: Map<string, FileUsage>;
 }
@@ -438,92 +438,6 @@ declare class DomainAggregator {
     private isEqual;
 }
 
-/**
- * Compiler
- *
- * Compiles hyperscript AST to JavaScript at build time.
- * Eliminates the need for runtime parsing.
- *
- * Multilingual support:
- * - For English: Uses HybridParser directly
- * - For other languages: Uses semantic parser to translate → AST → JavaScript
- * - Semantic parsing happens at BUILD time (zero runtime overhead)
- */
-
-/**
- * Result shape returned by the semantic parse function.
- * Matches `ParseWithConfidenceResult` from `@lokascript/semantic`.
- */
-interface SemanticParseResult {
-    confidence: number;
-    node?: unknown;
-    error?: string | undefined;
-}
-/**
- * Function that parses input in a given language and returns a confidence
- * score plus an optional semantic node. Matches `parseSemantic` / `parseWithConfidence`
- * from `@lokascript/semantic`.
- */
-type SemanticParseFn = (input: string, language: string) => SemanticParseResult;
-/**
- * Function that checks whether a language is registered for parsing.
- * Matches `isLanguageRegistered` from `@lokascript/semantic`.
- */
-type SupportsLanguageFn = (language: string) => boolean;
-type BuildASTFn = (node: unknown) => {
-    ast: ASTNode;
-    warnings: string[];
-};
-/**
- * Configure the semantic parser for multilingual compilation.
- *
- * @example
- * ```typescript
- * import { parseSemantic, isLanguageRegistered, buildAST } from '@lokascript/semantic';
- * import { setSemanticParser } from '@hyperfixi/vite-plugin';
- *
- * setSemanticParser(parseSemantic, isLanguageRegistered, buildAST);
- * ```
- */
-declare function setSemanticParser(parse: SemanticParseFn, supports: SupportsLanguageFn, buildAST: BuildASTFn): void;
-/**
- * Clear the semantic parser (for testing).
- */
-declare function clearSemanticParser(): void;
-/**
- * Check if semantic parser is available.
- */
-declare function hasSemanticParser(): boolean;
-interface CompiledHandler {
-    /** Unique handler ID (h0, h1, etc.) */
-    id: string;
-    /** Event name (click, input, etc.) */
-    event: string;
-    /** Event modifiers */
-    modifiers: {
-        prevent?: boolean;
-        stop?: boolean;
-        once?: boolean;
-        debounce?: number;
-        throttle?: number;
-    };
-    /** Compiled JavaScript code */
-    code: string;
-    /** Whether handler needs the mini-evaluator for dynamic expressions */
-    needsEvaluator: boolean;
-    /** Original hyperscript for debugging */
-    original: string;
-}
-/**
- * Compile options for multilingual support.
- */
-interface CompileOptions {
-    /** Language code (ISO 639-1). Defaults to 'en'. */
-    language?: string;
-    /** Enable debug logging. */
-    debug?: boolean;
-}
-
 /**
  * Language Keywords for Detection
  *
@@ -620,24 +534,16 @@ declare function getOptimalRegion(languages: Set<SupportedLanguage>): 'western'
  * })
  * ```
  *
- * @example
- * ```javascript
- * // Compile mode for smallest bundles (~500 bytes)
- * hyperfixi({
- *   mode: 'compile',  // Pre-compile hyperscript to JS
- *   debug: true,
- * })
- * ```
  */
 
 /**
  * Compute a hash of the current usage for dev-server cache invalidation.
  *
  * Every input that influences bundle SELECTION must be part of this hash.
- * The htmx/reactivity flags route to the hybrid-hx / hx-v4 tiers; before they
- * were hashed, adding or removing an hx-live/sse-connect/ws-send attribute —
- * without touching any command/block/language — left the cached dev bundle at
- * the wrong tier. Exported for tests.
+ * The htmx/reactivity flags decide which engine modules are registered; before
+ * they were hashed, adding or removing an hx-live/sse-connect/ws-send
+ * attribute — without touching any command/block/language — left the cached
+ * dev bundle stale. Exported for tests.
  */
 declare function computeUsageHash(usage: AggregatedUsage): string;
 /**
@@ -648,4 +554,4 @@ declare function computeUsageHash(usage: AggregatedUsage): string;
  */
 declare function hyperfixi(options?: HyperfixiPluginOptions): Plugin;
 
-export { type AggregatedUsage, type CompileOptions, type CompiledHandler, type CustomLanguageKeywords, type DomainAggregatedUsage, DomainAggregator, type DomainFileUsage, type DomainScanRule, DomainScanner, type FileUsage, type HyperfixiPluginOptions, REGIONS, SUPPORTED_LANGUAGES, type ServerBridgeOptions, type SupportedLanguage, clearCustomKeywords, clearSemanticParser, computeUsageHash, hyperfixi as default, descriptorToScanRule, detectLanguages, getAllLanguageCodes, getKeywordsForLanguage, getOptimalRegion, hasSemanticParser, hyperfixi, isNonLatinLanguage, registerCustomKeywords, setSemanticParser };
+export { type AggregatedUsage, type CustomLanguageKeywords, type DomainAggregatedUsage, DomainAggregator, type DomainFileUsage, type DomainScanRule, DomainScanner, type FileUsage, type HyperfixiPluginOptions, REGIONS, SUPPORTED_LANGUAGES, type ServerBridgeOptions, type SupportedLanguage, clearCustomKeywords, computeUsageHash, hyperfixi as default, descriptorToScanRule, detectLanguages, getAllLanguageCodes, getKeywordsForLanguage, getOptimalRegion, hyperfixi, isNonLatinLanguage, registerCustomKeywords };