@weasel-js/forge 1.9.4 → 1.10.1

package/dist/test/index.d.ts

@@ -1,4 +1,4 @@
-import { F as FrameSetup } from '../FrameController-BQjKhdwk.js';
+import { F as FrameSetup } from '../FrameController-UeTY7ubF.js';
 import '@weasel-js/labkit/config';
 import 'react';
 

package/dist/test/index.js

@@ -1,10 +1,10 @@
-import { StoryTrial } from '../chunk-ZZCCIXEJ.js';
-import '../chunk-JHL4ERDA.js';
-import { loadStories } from '../chunk-B3PPHJTS.js';
+import { StoryTrial } from '../chunk-E2FHBDNQ.js';
+import '../chunk-DFKCLZKS.js';
+import { loadStories } from '../chunk-AP3DRQLI.js';
 import '../chunk-L5XM5VKB.js';
-import '../chunk-HRGPFQBW.js';
-import '../chunk-5KI5YSQ5.js';
-import '../chunk-TXLWQFF6.js';
+import '../chunk-ZAWXMUGZ.js';
+import '../chunk-GB6PRJET.js';
+import '../chunk-FL2MUPUL.js';
 import { withValueAtPath } from '@weasel-js/labkit/config';
 import { useState, useEffect } from 'react';
 import { createRoot } from 'react-dom/client';

package/dist/test/play.d.ts

@@ -5,12 +5,10 @@ export { default as userEvent } from '@testing-library/user-event';
 /**
  * What a CSF `play` function asserts with.
  *
- * A play runs in the test page beside the story — a real browser document,
- * driven by `forgeTest` under vitest; the workshop never runs one — so it
- * cannot import `vitest`, whose entry only exists inside a test worker. This module assembles the same
+ * A play runs in the test page beside the story, so it cannot import `vitest`,
+ * whose entry only exists inside a test worker. This module assembles the same
  * `expect` vitest hands a test: chai carrying `@vitest/expect`'s jest-style
- * matchers. Queries and input come from testing-library, which is already
- * browser-only.
+ * matchers.
  *
  * No jest-dom matchers. They install through `expect.extend`, which wants the
  * matcher state a test worker sets up, and there is none here — the call

package/dist/test/play.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/test/play.ts"],"names":["expect"],"mappings":";;;;;;AAmBK,IAAA,CAAA,GAAA,CAAI,UAAU,CAAA;AACd,IAAA,CAAA,GAAA,CAAI,cAAc,CAAA;AAClB,IAAA,CAAA,GAAA,CAAI,sBAAsB,CAAA;AAGxB,IAAMA,OAAAA,GAAc,IAAA,CAAA","file":"play.js","sourcesContent":["/**\n * What a CSF `play` function asserts with.\n *\n * A play runs in the test page beside the story — a real browser document,\n * driven by `forgeTest` under vitest; the workshop never runs one — so it\n * cannot import `vitest`, whose entry only exists inside a test worker. This module assembles the same\n * `expect` vitest hands a test: chai carrying `@vitest/expect`'s jest-style\n * matchers. Queries and input come from testing-library, which is already\n * browser-only.\n *\n * No jest-dom matchers. They install through `expect.extend`, which wants the\n * matcher state a test worker sets up, and there is none here — the call\n * throws at module scope. Assert on the DOM directly instead:\n * `expect(el.textContent).toBe(…)` for `toHaveTextContent`,\n * `expect(el).not.toBeNull()` for `toBeInTheDocument`.\n */\nimport { type ExpectStatic, JestAsymmetricMatchers, JestChaiExpect, JestExtend } from '@vitest/expect';\nimport * as chai from 'chai';\n\nchai.use(JestExtend);\nchai.use(JestChaiExpect);\nchai.use(JestAsymmetricMatchers);\n\n/** `expect`, with jest's matchers. */\nexport const expect = chai.expect as unknown as ExpectStatic;\n\nexport { screen, waitFor, within } from '@testing-library/dom';\nexport { default as userEvent } from '@testing-library/user-event';\n"]}
+{"version":3,"sources":["../../src/test/play.ts"],"names":["expect"],"mappings":";;;;;;AAiBK,IAAA,CAAA,GAAA,CAAI,UAAU,CAAA;AACd,IAAA,CAAA,GAAA,CAAI,cAAc,CAAA;AAClB,IAAA,CAAA,GAAA,CAAI,sBAAsB,CAAA;AAGxB,IAAMA,OAAAA,GAAc,IAAA,CAAA","file":"play.js","sourcesContent":["/**\n * What a CSF `play` function asserts with.\n *\n * A play runs in the test page beside the story, so it cannot import `vitest`,\n * whose entry only exists inside a test worker. This module assembles the same\n * `expect` vitest hands a test: chai carrying `@vitest/expect`'s jest-style\n * matchers.\n *\n * No jest-dom matchers. They install through `expect.extend`, which wants the\n * matcher state a test worker sets up, and there is none here — the call\n * throws at module scope. Assert on the DOM directly instead:\n * `expect(el.textContent).toBe(…)` for `toHaveTextContent`,\n * `expect(el).not.toBeNull()` for `toBeInTheDocument`.\n */\nimport { type ExpectStatic, JestAsymmetricMatchers, JestChaiExpect, JestExtend } from '@vitest/expect';\nimport * as chai from 'chai';\n\nchai.use(JestExtend);\nchai.use(JestChaiExpect);\nchai.use(JestAsymmetricMatchers);\n\n/** `expect`, with jest's matchers. */\nexport const expect = chai.expect as unknown as ExpectStatic;\n\nexport { screen, waitFor, within } from '@testing-library/dom';\nexport { default as userEvent } from '@testing-library/user-event';\n"]}

package/dist/vite/index.d.ts

@@ -1,5 +1,14 @@
 import { Plugin } from 'vite';
 
+/** Narrows which props get a control. */
+interface PropControlsOptions {
+    /**
+     * Leaves out a prop declared in a file this answers true for, given the file's absolute path. Props that React's
+     * types or TypeScript's libraries declare are always left out.
+     */
+    skip?: (declaredIn: string) => boolean;
+}
+
 /** Options for the `forge` vite plugin. */
 interface ForgeOptions {
     /** Globs of story files, relative to the vite root. */
@@ -12,6 +21,12 @@ interface ForgeOptions {
     frameStyles?: string[];
     /** Alias Storybook's runtime modules to forge shims. Default true. */
     storybookShims?: boolean;
+    /**
+     * Give a CSF story a control for each prop of its meta's `component`, read from the component's TypeScript types;
+     * the story's own `args` and `argTypes` refine them. Needs `typescript` installed. Default true; an object narrows
+     * which props are read.
+     */
+    propControls?: boolean | PropControlsOptions;
 }
 /**
  * The vite plugin that serves the workshop: it indexes the story files, serves the workshop at `/` and the frame
@@ -34,4 +49,16 @@ interface ForgeTestOptions {
  */
 declare function forgeTest(options: ForgeTestOptions): Plugin[];
 
-export { type ForgeOptions, type ForgeTestOptions, forge, forgeTest };
+/** Options for the `watchProbe` vite plugin. */
+interface WatchProbeOptions {
+    /**
+     * Answers whether the OS is reporting file changes: false makes the plugin log its warning. Called once, as the
+     * dev server starts, and not at all where the server polls or does not watch. Default: {@link fileEventsArrive},
+     * which writes a temp file and waits five seconds for the report.
+     */
+    probe?: () => Promise<boolean>;
+}
+/** A plugin giving any dev server the warning forge's own gives when the OS reports no file changes. */
+declare function watchProbe({ probe }?: WatchProbeOptions): Plugin;
+
+export { type ForgeOptions, type ForgeTestOptions, type PropControlsOptions, type WatchProbeOptions, forge, forgeTest, watchProbe };