@fictjs/compiler 0.2.3 → 0.3.0

package/dist/index.d.cts

@@ -52,6 +52,18 @@ interface FictCompilerOptions {
      * If omitted, the compiler uses a process-wide cache.
      */
     moduleMetadata?: Map<string, ModuleReactiveMetadata>;
+    /**
+     * Emit module metadata sidecar files to enable cross-process metadata resolution.
+     * - true: always emit
+     * - false: never emit
+     * - 'auto' or undefined: emit only when no external metadata store/resolver is provided
+     */
+    emitModuleMetadata?: boolean | 'auto';
+    /**
+     * File extension suffix for module metadata sidecars.
+     * Defaults to '.fict.meta.json'.
+     */
+    moduleMetadataExtension?: string;
     /**
      * Optional hook to resolve module metadata for a given import source.
      * Tooling can override the default resolution strategy.
@@ -67,6 +79,31 @@ interface FictCompilerOptions {
         projectVersion?: number;
         configPath?: string;
     };
+    /**
+     * Function names that create reactive scopes. Callbacks passed to these functions
+     * are treated as component-like contexts where $state and $effect can be used.
+     *
+     * This is useful for testing libraries (e.g., renderHook) and other scenarios
+     * where reactive code runs in non-component contexts.
+     *
+     * Limitations (by design):
+     * - Only direct calls are recognized (e.g., renderHook(() => ...), utils.renderHook(() => ...)).
+     * - Only the first argument is treated as the reactive callback.
+     * - Aliased/indirect calls are not recognized (e.g., const rh = renderHook; rh(() => ...)).
+     *
+     * @example
+     * ```typescript
+     * // In vite.config.ts or babel config:
+     * reactiveScopes: ['renderHook', 'createReactiveScope']
+     *
+     * // Then in tests:
+     * renderHook(() => {
+     *   let count = $state(0)  // Now allowed!
+     *   return count
+     * })
+     * ```
+     */
+    reactiveScopes?: string[];
 }
 
 declare function resolveModuleMetadata(source: string, importer: string | undefined, options?: FictCompilerOptions): ModuleReactiveMetadata | undefined;

package/dist/index.d.ts

@@ -52,6 +52,18 @@ interface FictCompilerOptions {
      * If omitted, the compiler uses a process-wide cache.
      */
     moduleMetadata?: Map<string, ModuleReactiveMetadata>;
+    /**
+     * Emit module metadata sidecar files to enable cross-process metadata resolution.
+     * - true: always emit
+     * - false: never emit
+     * - 'auto' or undefined: emit only when no external metadata store/resolver is provided
+     */
+    emitModuleMetadata?: boolean | 'auto';
+    /**
+     * File extension suffix for module metadata sidecars.
+     * Defaults to '.fict.meta.json'.
+     */
+    moduleMetadataExtension?: string;
     /**
      * Optional hook to resolve module metadata for a given import source.
      * Tooling can override the default resolution strategy.
@@ -67,6 +79,31 @@ interface FictCompilerOptions {
         projectVersion?: number;
         configPath?: string;
     };
+    /**
+     * Function names that create reactive scopes. Callbacks passed to these functions
+     * are treated as component-like contexts where $state and $effect can be used.
+     *
+     * This is useful for testing libraries (e.g., renderHook) and other scenarios
+     * where reactive code runs in non-component contexts.
+     *
+     * Limitations (by design):
+     * - Only direct calls are recognized (e.g., renderHook(() => ...), utils.renderHook(() => ...)).
+     * - Only the first argument is treated as the reactive callback.
+     * - Aliased/indirect calls are not recognized (e.g., const rh = renderHook; rh(() => ...)).
+     *
+     * @example
+     * ```typescript
+     * // In vite.config.ts or babel config:
+     * reactiveScopes: ['renderHook', 'createReactiveScope']
+     *
+     * // Then in tests:
+     * renderHook(() => {
+     *   let count = $state(0)  // Now allowed!
+     *   return count
+     * })
+     * ```
+     */
+    reactiveScopes?: string[];
 }
 
 declare function resolveModuleMetadata(source: string, importer: string | undefined, options?: FictCompilerOptions): ModuleReactiveMetadata | undefined;