@hyperfixi/vite-plugin 2.3.1 → 2.4.0

package/dist/index.d.cts

@@ -111,7 +111,7 @@ interface HyperfixiPluginOptions {
      * - 'slavic': pl, ru, uk
      * - 'south-asian': hi, bn
      * - 'priority': 13 most common languages
-     * - 'all': All 21 supported languages
+     * - 'all': All 24 supported languages
      */
     region?: 'western' | 'east-asian' | 'slavic' | 'south-asian' | 'priority' | 'all';
     /**
@@ -209,6 +209,29 @@ interface HtmxUsage {
     urlManagement: Set<string>;
     /** Whether hx-confirm is used */
     usesConfirm: 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.
+     *
+     * 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`. */
+    needsSSE?: boolean;
+    /** ws-connect / ws-send detected. Pulls in `@hyperfixi/core/htmx/ws`. */
+    needsWS?: boolean;
+    /**
+     * `bind $x to <expr>.<prop>` detected inside an `_=` attribute. Implies
+     * reactivity (the bind feature lives in `@hyperfixi/reactivity`).
+     */
+    needsBindToProperty?: boolean;
+    /**
+     * Any hx-v4-class feature → vite-generated bundle should auto-install
+     * `@hyperfixi/reactivity`. Derived from needsHxLive || needsBindToProperty.
+     */
+    needsReactivity?: boolean;
 }
 /**
  * Usage information detected from a single file
@@ -224,6 +247,26 @@ interface FileUsage {
     detectedLanguages: Set<string>;
     /** HTMX/Fixi attribute usage (if detected) */
     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`.
+     *
+     * Kept top-level rather than under `htmx` because authors may use these
+     * features without any htmx attributes at all (pure `_=` reactive code).
+     * The aggregator OR-merges this with `htmx.needsReactivity`.
+     *
+     * Optional so older callers / fixtures that build `FileUsage` literals
+     * without these fields stay valid; the scanner always emits explicit
+     * `false` so reads can rely on the value being defined post-scan.
+     */
+    needsReactivity?: boolean;
+    /**
+     * Explicit-property `bind` form (`bind $x to <expr>.<prop>`) detected
+     * in an `_=` body. Implies `needsReactivity` too.
+     */
+    needsBindToProperty?: boolean;
 }
 /**
  * Aggregated usage information across all files
@@ -239,6 +282,17 @@ interface AggregatedUsage {
     detectedLanguages: Set<string>;
     /** Aggregated HTMX/Fixi usage across all files */
     htmx: HtmxUsage;
+    /**
+     * 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`.
+     *
+     * Optional to keep test fixtures compatible; the aggregator always
+     * emits an explicit boolean.
+     */
+    needsReactivity?: boolean;
+    /** Whether any file uses explicit-property bind. */
+    needsBindToProperty?: boolean;
     /** Map of file paths to their usage */
     fileUsage: Map<string, FileUsage>;
 }
@@ -392,35 +446,41 @@ declare class DomainAggregator {
  */
 
 /**
- * Semantic analyzer interface for multilingual support.
- * This matches the interface from @lokascript/semantic.
+ * Result shape returned by the semantic parse function.
+ * Matches `ParseWithConfidenceResult` from `@lokascript/semantic`.
  */
-interface SemanticAnalysisResult {
+interface SemanticParseResult {
     confidence: number;
     node?: unknown;
-    errors?: string[];
-}
-interface SemanticAnalyzer {
-    analyze(input: string, language: string): SemanticAnalysisResult;
-    supportsLanguage(language: string): boolean;
+    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.
- * Call this with the semantic analyzer from @lokascript/semantic.
  *
  * @example
  * ```typescript
- * import { createSemanticAnalyzer, buildAST } from '@lokascript/semantic';
+ * import { parseSemantic, isLanguageRegistered, buildAST } from '@lokascript/semantic';
  * import { setSemanticParser } from '@hyperfixi/vite-plugin';
  *
- * setSemanticParser(createSemanticAnalyzer(), buildAST);
+ * setSemanticParser(parseSemantic, isLanguageRegistered, buildAST);
  * ```
  */
-declare function setSemanticParser(analyzer: SemanticAnalyzer, buildAST: BuildASTFn): void;
+declare function setSemanticParser(parse: SemanticParseFn, supports: SupportsLanguageFn, buildAST: BuildASTFn): void;
 /**
  * Clear the semantic parser (for testing).
  */
@@ -462,7 +522,7 @@ interface CompileOptions {
 /**
  * Language Keywords for Detection
  *
- * Maps of keywords for each of the 21 supported languages.
+ * Maps of keywords for each of the 24 supported languages.
  * Used by the scanner to detect which languages are used in hyperscript templates.
  *
  * Note: These are a representative subset of keywords - enough to reliably
@@ -472,7 +532,7 @@ interface CompileOptions {
 /**
  * All supported language codes.
  */
-declare const SUPPORTED_LANGUAGES: readonly ["en", "es", "pt", "fr", "de", "it", "vi", "pl", "ru", "uk", "ja", "zh", "ko", "ar", "hi", "bn", "th", "tr", "id", "sw", "qu", "tl"];
+declare const SUPPORTED_LANGUAGES: readonly ["en", "es", "pt", "fr", "de", "it", "vi", "pl", "ru", "uk", "ja", "zh", "ko", "ar", "he", "hi", "bn", "th", "tr", "id", "ms", "sw", "qu", "tl"];
 type SupportedLanguage = (typeof SUPPORTED_LANGUAGES)[number];
 /**
  * Regional bundle mappings.

package/dist/index.d.ts

@@ -111,7 +111,7 @@ interface HyperfixiPluginOptions {
      * - 'slavic': pl, ru, uk
      * - 'south-asian': hi, bn
      * - 'priority': 13 most common languages
-     * - 'all': All 21 supported languages
+     * - 'all': All 24 supported languages
      */
     region?: 'western' | 'east-asian' | 'slavic' | 'south-asian' | 'priority' | 'all';
     /**
@@ -209,6 +209,29 @@ interface HtmxUsage {
     urlManagement: Set<string>;
     /** Whether hx-confirm is used */
     usesConfirm: 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.
+     *
+     * 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`. */
+    needsSSE?: boolean;
+    /** ws-connect / ws-send detected. Pulls in `@hyperfixi/core/htmx/ws`. */
+    needsWS?: boolean;
+    /**
+     * `bind $x to <expr>.<prop>` detected inside an `_=` attribute. Implies
+     * reactivity (the bind feature lives in `@hyperfixi/reactivity`).
+     */
+    needsBindToProperty?: boolean;
+    /**
+     * Any hx-v4-class feature → vite-generated bundle should auto-install
+     * `@hyperfixi/reactivity`. Derived from needsHxLive || needsBindToProperty.
+     */
+    needsReactivity?: boolean;
 }
 /**
  * Usage information detected from a single file
@@ -224,6 +247,26 @@ interface FileUsage {
     detectedLanguages: Set<string>;
     /** HTMX/Fixi attribute usage (if detected) */
     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`.
+     *
+     * Kept top-level rather than under `htmx` because authors may use these
+     * features without any htmx attributes at all (pure `_=` reactive code).
+     * The aggregator OR-merges this with `htmx.needsReactivity`.
+     *
+     * Optional so older callers / fixtures that build `FileUsage` literals
+     * without these fields stay valid; the scanner always emits explicit
+     * `false` so reads can rely on the value being defined post-scan.
+     */
+    needsReactivity?: boolean;
+    /**
+     * Explicit-property `bind` form (`bind $x to <expr>.<prop>`) detected
+     * in an `_=` body. Implies `needsReactivity` too.
+     */
+    needsBindToProperty?: boolean;
 }
 /**
  * Aggregated usage information across all files
@@ -239,6 +282,17 @@ interface AggregatedUsage {
     detectedLanguages: Set<string>;
     /** Aggregated HTMX/Fixi usage across all files */
     htmx: HtmxUsage;
+    /**
+     * 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`.
+     *
+     * Optional to keep test fixtures compatible; the aggregator always
+     * emits an explicit boolean.
+     */
+    needsReactivity?: boolean;
+    /** Whether any file uses explicit-property bind. */
+    needsBindToProperty?: boolean;
     /** Map of file paths to their usage */
     fileUsage: Map<string, FileUsage>;
 }
@@ -392,35 +446,41 @@ declare class DomainAggregator {
  */
 
 /**
- * Semantic analyzer interface for multilingual support.
- * This matches the interface from @lokascript/semantic.
+ * Result shape returned by the semantic parse function.
+ * Matches `ParseWithConfidenceResult` from `@lokascript/semantic`.
  */
-interface SemanticAnalysisResult {
+interface SemanticParseResult {
     confidence: number;
     node?: unknown;
-    errors?: string[];
-}
-interface SemanticAnalyzer {
-    analyze(input: string, language: string): SemanticAnalysisResult;
-    supportsLanguage(language: string): boolean;
+    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.
- * Call this with the semantic analyzer from @lokascript/semantic.
  *
  * @example
  * ```typescript
- * import { createSemanticAnalyzer, buildAST } from '@lokascript/semantic';
+ * import { parseSemantic, isLanguageRegistered, buildAST } from '@lokascript/semantic';
  * import { setSemanticParser } from '@hyperfixi/vite-plugin';
  *
- * setSemanticParser(createSemanticAnalyzer(), buildAST);
+ * setSemanticParser(parseSemantic, isLanguageRegistered, buildAST);
  * ```
  */
-declare function setSemanticParser(analyzer: SemanticAnalyzer, buildAST: BuildASTFn): void;
+declare function setSemanticParser(parse: SemanticParseFn, supports: SupportsLanguageFn, buildAST: BuildASTFn): void;
 /**
  * Clear the semantic parser (for testing).
  */
@@ -462,7 +522,7 @@ interface CompileOptions {
 /**
  * Language Keywords for Detection
  *
- * Maps of keywords for each of the 21 supported languages.
+ * Maps of keywords for each of the 24 supported languages.
  * Used by the scanner to detect which languages are used in hyperscript templates.
  *
  * Note: These are a representative subset of keywords - enough to reliably
@@ -472,7 +532,7 @@ interface CompileOptions {
 /**
  * All supported language codes.
  */
-declare const SUPPORTED_LANGUAGES: readonly ["en", "es", "pt", "fr", "de", "it", "vi", "pl", "ru", "uk", "ja", "zh", "ko", "ar", "hi", "bn", "th", "tr", "id", "sw", "qu", "tl"];
+declare const SUPPORTED_LANGUAGES: readonly ["en", "es", "pt", "fr", "de", "it", "vi", "pl", "ru", "uk", "ja", "zh", "ko", "ar", "he", "hi", "bn", "th", "tr", "id", "ms", "sw", "qu", "tl"];
 type SupportedLanguage = (typeof SUPPORTED_LANGUAGES)[number];
 /**
  * Regional bundle mappings.