@ng-prism/core 22.2.1 → 22.4.0

package/dist/shared/measure.type.d.ts

@@ -0,0 +1,52 @@
+/**
+ * The measuring tool measures geometry, not cascade: a point knows the edge
+ * it sits on, but not the CSS property that produced it. Mapping pixels to a
+ * property is deliberately a follow-up step, see Spec §13.
+ */
+export type SnapKind = 'border' | 'padding' | 'content';
+export type EdgeSide = 'top' | 'right' | 'bottom' | 'left';
+/** What a point snapped to — `null` when no target was within tolerance. */
+export interface SnapRef {
+    kind: SnapKind;
+    side: EdgeSide;
+    from: Element;
+}
+/**
+ * A measure point in `.demo-wrap`-local CSS pixels.
+ *
+ * Not in screen coordinates: `.demo-wrap` carries
+ * `transform: scale(var(--zoom))`, and local coordinates turn the distance
+ * into a CSS-pixel distance with no further division. Zooming after a pin is
+ * placed then does not shift it relative to the specimen.
+ */
+export interface MeasurePoint {
+    x: number;
+    y: number;
+    snap: SnapRef | null;
+}
+export interface Measurement {
+    a: MeasurePoint;
+    b: MeasurePoint;
+}
+/**
+ * How close the pointer has to come to an edge, in **screen** pixels.
+ *
+ * Screen and not document pixels, because the tolerance describes a
+ * precision of the hand and not a property of the document: it has to feel
+ * the same at 50% zoom as at 200%. Same value as `VIEWPORT_SNAP_TOLERANCE`,
+ * for the same reason.
+ */
+export declare const MEASURE_SNAP_TOLERANCE = 8;
+/**
+ * The span, in CSS pixels, above which the value fits between the end ticks.
+ *
+ * Below it the ticks and the number overlap, and the measurement becomes
+ * unreadable exactly where it needs to be most precise. The value then
+ * moves outside instead.
+ */
+export declare const MEASURE_LABEL_MIN_SPAN = 28;
+/** How far the value steps aside, perpendicular to the line, for short spans. */
+export declare const MEASURE_LABEL_OFFSET = 15;
+/** Length of an end tick, centered on the endpoint. */
+export declare const MEASURE_TICK_LENGTH = 7;
+//# sourceMappingURL=measure.type.d.ts.map

package/dist/shared/measure.type.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"measure.type.d.ts","sourceRoot":"","sources":["../../src/shared/measure.type.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,MAAM,MAAM,QAAQ,GAAG,QAAQ,GAAG,SAAS,GAAG,SAAS,CAAC;AAExD,MAAM,MAAM,QAAQ,GAAG,KAAK,GAAG,OAAO,GAAG,QAAQ,GAAG,MAAM,CAAC;AAE3D,4EAA4E;AAC5E,MAAM,WAAW,OAAO;IACpB,IAAI,EAAE,QAAQ,CAAC;IACf,IAAI,EAAE,QAAQ,CAAC;IACf,IAAI,EAAE,OAAO,CAAC;CACjB;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,YAAY;IACzB,CAAC,EAAE,MAAM,CAAC;IACV,CAAC,EAAE,MAAM,CAAC;IACV,IAAI,EAAE,OAAO,GAAG,IAAI,CAAC;CACxB;AAED,MAAM,WAAW,WAAW;IACxB,CAAC,EAAE,YAAY,CAAC;IAChB,CAAC,EAAE,YAAY,CAAC;CACnB;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,sBAAsB,IAAI,CAAC;AAExC;;;;;;GAMG;AACH,eAAO,MAAM,sBAAsB,KAAK,CAAC;AAEzC,iFAAiF;AACjF,eAAO,MAAM,oBAAoB,KAAK,CAAC;AAEvC,uDAAuD;AACvD,eAAO,MAAM,mBAAmB,IAAI,CAAC"}

package/dist/shared/measure.type.js

@@ -0,0 +1,21 @@
+/**
+ * How close the pointer has to come to an edge, in **screen** pixels.
+ *
+ * Screen and not document pixels, because the tolerance describes a
+ * precision of the hand and not a property of the document: it has to feel
+ * the same at 50% zoom as at 200%. Same value as `VIEWPORT_SNAP_TOLERANCE`,
+ * for the same reason.
+ */
+export const MEASURE_SNAP_TOLERANCE = 8;
+/**
+ * The span, in CSS pixels, above which the value fits between the end ticks.
+ *
+ * Below it the ticks and the number overlap, and the measurement becomes
+ * unreadable exactly where it needs to be most precise. The value then
+ * moves outside instead.
+ */
+export const MEASURE_LABEL_MIN_SPAN = 28;
+/** How far the value steps aside, perpendicular to the line, for short spans. */
+export const MEASURE_LABEL_OFFSET = 15;
+/** Length of an end tick, centered on the endpoint. */
+export const MEASURE_TICK_LENGTH = 7;

package/dist/shared/variant-bg.d.ts

@@ -2,37 +2,26 @@ import type { CanvasBg } from './canvas-bg.type.js';
 /**
  * The surface a variant is reported to render on when nothing declares one.
  *
- * An undeclared variant is the "no opinion" case, and `transparent` is the
- * honest capture of no opinion. The alternative, `checker`, patterns over
- * `--prism-bg-surface` — a *theme* token — and capture mode strips the pattern
- * and keeps the colour, so an undeclared variant used to be photographed on
- * whichever theme the runner's browser happened to start in. That is not a
- * neutral default; it is the runner's theme leaking into a baseline. Alpha
- * carries no such dependency, and it is not the thing capture mode's
- * determinism argument rules out: a pattern has a phase that shifts when a
- * centred component resizes, an alpha channel is a per-pixel value that does
- * not move.
- *
- * In the app both values look identical — `transparent` renders as the same
- * checkerboard, which is the UI's way of saying "no surface here". The change
- * is only visible in a capture.
- *
- * The cost is real and worth stating plainly: a runner that does not pass
- * `omitBackground: true` gets an opaque capture over whatever the browser
- * painted, because the page's own backdrop is below every stylesheet. See
+ * `transparent`, because an undeclared variant has no opinion about its
+ * surface. `checker` patterns over `--prism-bg-surface`, a theme token, and
+ * capture mode keeps the colour, so the runner's theme would leak into the
+ * baseline. Alpha has no such dependency and, unlike a pattern, does not shift
+ * when a centred component resizes. In the app both render the same
+ * checkerboard; the difference only shows in a capture.
+ *
+ * A runner must pass `omitBackground: true`, otherwise the capture is opaque
+ * over whatever the browser painted. See
  * `docs/guide/visual-regression.md#capturing-transparency`.
  *
- * What to declare, now that the default no longer decides it for you:
+ * What to declare:
  *
- * - `light` or `dark` when the component was designed against a surface.
- *   Their colours are absolute rather than theme tokens, which is what makes
- *   them stable across runners.
- * - `transparent` when the component's own transparency is the thing under
- *   test — an outlined button, an icon, a divider. Flattening one onto an
- *   opaque colour makes a transparent fill and a painted fill produce the
- *   same pixels.
- * - `dots`, `plain` or `checker` for browsing. All three follow the active
- *   theme, so a baseline recorded on one is only as stable as the theme.
+ * - `light` or `dark` when the component was designed against a surface. Their
+ *   colours are absolute, not theme tokens, so they are stable across runners.
+ * - `transparent` when the component's own transparency is under test (an
+ *   outlined button, an icon, a divider). On an opaque colour a transparent
+ *   fill and a painted fill produce the same pixels.
+ * - `dots`, `plain` or `checker` for browsing. They follow the active theme, so
+ *   a baseline recorded on one is only as stable as the theme.
  */
 export declare const DEFAULT_VARIANT_BG: CanvasBg;
 /**
@@ -50,7 +39,7 @@ export interface VariantBgSource {
 /**
  * The background a variant *declares*, or `null` when it declares none.
  *
- * Priority is variant, then component. `null` is a meaningful answer — it is
+ * Priority is variant, then component. `null` is a meaningful answer. It is
  * what lets the canvas keep the user's own background choice instead of
  * overwriting it, and what makes the background pill able to say "this is your
  * choice, not the component's".
@@ -64,8 +53,8 @@ export declare function declaredVariantBg(config: VariantBgSource, variantIndex:
 /**
  * The background a variant renders on, always resolved to a concrete value.
  *
- * This is the answer external tooling needs — a screenshot runner cannot act
- * on "nothing declared" — and the one capture mode paints, so the value
+ * This is the answer external tooling needs, since a screenshot runner cannot act
+ * on "nothing declared". It is also what capture mode paints, so the value
  * reported by `__PRISM_MANIFEST__` and the pixels in the capture agree.
  */
 export declare function resolveVariantBg(config: VariantBgSource, variantIndex: number): CanvasBg;

package/dist/shared/variant-bg.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"variant-bg.d.ts","sourceRoot":"","sources":["../../src/shared/variant-bg.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,eAAO,MAAM,kBAAkB,EAAE,QAAwB,CAAC;AAE1D;;;;;GAKG;AACH,MAAM,WAAW,eAAe;IAC9B,EAAE,CAAC,EAAE,QAAQ,CAAC;IACd,QAAQ,CAAC,EAAE,SAAS;QAAE,EAAE,CAAC,EAAE,QAAQ,CAAA;KAAE,EAAE,CAAC;CACzC;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,iBAAiB,CAC/B,MAAM,EAAE,eAAe,EACvB,YAAY,EAAE,MAAM,GACnB,QAAQ,GAAG,IAAI,CAEjB;AAED;;;;;;GAMG;AACH,wBAAgB,gBAAgB,CAC9B,MAAM,EAAE,eAAe,EACvB,YAAY,EAAE,MAAM,GACnB,QAAQ,CAEV"}
+{"version":3,"file":"variant-bg.d.ts","sourceRoot":"","sources":["../../src/shared/variant-bg.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,eAAO,MAAM,kBAAkB,EAAE,QAAwB,CAAC;AAE1D;;;;;GAKG;AACH,MAAM,WAAW,eAAe;IAC5B,EAAE,CAAC,EAAE,QAAQ,CAAC;IACd,QAAQ,CAAC,EAAE,SAAS;QAAE,EAAE,CAAC,EAAE,QAAQ,CAAA;KAAE,EAAE,CAAC;CAC3C;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,GAAG,QAAQ,GAAG,IAAI,CAEhG;AAED;;;;;;GAMG;AACH,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,eAAe,EAAE,YAAY,EAAE,MAAM,GAAG,QAAQ,CAExF"}

package/dist/shared/variant-bg.js

@@ -1,43 +1,32 @@
 /**
  * The surface a variant is reported to render on when nothing declares one.
  *
- * An undeclared variant is the "no opinion" case, and `transparent` is the
- * honest capture of no opinion. The alternative, `checker`, patterns over
- * `--prism-bg-surface` — a *theme* token — and capture mode strips the pattern
- * and keeps the colour, so an undeclared variant used to be photographed on
- * whichever theme the runner's browser happened to start in. That is not a
- * neutral default; it is the runner's theme leaking into a baseline. Alpha
- * carries no such dependency, and it is not the thing capture mode's
- * determinism argument rules out: a pattern has a phase that shifts when a
- * centred component resizes, an alpha channel is a per-pixel value that does
- * not move.
- *
- * In the app both values look identical — `transparent` renders as the same
- * checkerboard, which is the UI's way of saying "no surface here". The change
- * is only visible in a capture.
- *
- * The cost is real and worth stating plainly: a runner that does not pass
- * `omitBackground: true` gets an opaque capture over whatever the browser
- * painted, because the page's own backdrop is below every stylesheet. See
+ * `transparent`, because an undeclared variant has no opinion about its
+ * surface. `checker` patterns over `--prism-bg-surface`, a theme token, and
+ * capture mode keeps the colour, so the runner's theme would leak into the
+ * baseline. Alpha has no such dependency and, unlike a pattern, does not shift
+ * when a centred component resizes. In the app both render the same
+ * checkerboard; the difference only shows in a capture.
+ *
+ * A runner must pass `omitBackground: true`, otherwise the capture is opaque
+ * over whatever the browser painted. See
  * `docs/guide/visual-regression.md#capturing-transparency`.
  *
- * What to declare, now that the default no longer decides it for you:
+ * What to declare:
  *
- * - `light` or `dark` when the component was designed against a surface.
- *   Their colours are absolute rather than theme tokens, which is what makes
- *   them stable across runners.
- * - `transparent` when the component's own transparency is the thing under
- *   test — an outlined button, an icon, a divider. Flattening one onto an
- *   opaque colour makes a transparent fill and a painted fill produce the
- *   same pixels.
- * - `dots`, `plain` or `checker` for browsing. All three follow the active
- *   theme, so a baseline recorded on one is only as stable as the theme.
+ * - `light` or `dark` when the component was designed against a surface. Their
+ *   colours are absolute, not theme tokens, so they are stable across runners.
+ * - `transparent` when the component's own transparency is under test (an
+ *   outlined button, an icon, a divider). On an opaque colour a transparent
+ *   fill and a painted fill produce the same pixels.
+ * - `dots`, `plain` or `checker` for browsing. They follow the active theme, so
+ *   a baseline recorded on one is only as stable as the theme.
  */
 export const DEFAULT_VARIANT_BG = 'transparent';
 /**
  * The background a variant *declares*, or `null` when it declares none.
  *
- * Priority is variant, then component. `null` is a meaningful answer — it is
+ * Priority is variant, then component. `null` is a meaningful answer. It is
  * what lets the canvas keep the user's own background choice instead of
  * overwriting it, and what makes the background pill able to say "this is your
  * choice, not the component's".
@@ -53,8 +42,8 @@ export function declaredVariantBg(config, variantIndex) {
 /**
  * The background a variant renders on, always resolved to a concrete value.
  *
- * This is the answer external tooling needs — a screenshot runner cannot act
- * on "nothing declared" — and the one capture mode paints, so the value
+ * This is the answer external tooling needs, since a screenshot runner cannot act
+ * on "nothing declared". It is also what capture mode paints, so the value
  * reported by `__PRISM_MANIFEST__` and the pixels in the capture agree.
  */
 export function resolveVariantBg(config, variantIndex) {

package/dist/shared/viewport.type.d.ts

@@ -0,0 +1,43 @@
+/**
+ * The canvas viewport: one nullable number, not a device list.
+ *
+ * The tool is for finding where a layout breaks, so the presets are plain
+ * widths without device names. A device name would suggest a simulation; the
+ * constraint only narrows the box. Media queries still read the real browser
+ * viewport; only `@container` rules respond.
+ */
+/**
+ * The narrowest the constraint will go.
+ *
+ * Below any real device. The presets cover the widths people design against;
+ * the floor lets a drag go past them to find where a layout breaks. A floor at
+ * the narrowest real phone would hide that point for the components most worth
+ * checking.
+ */
+export declare const VIEWPORT_MIN = 100;
+/** Wide enough for a desktop breakpoint, short of the point where the stage scrolls on any realistic screen. */
+export declare const VIEWPORT_MAX = 1600;
+/** Where the toggle lands when no width has been set this session. */
+export declare const VIEWPORT_DEFAULT = 390;
+/** How near a drag has to come before it rests on a preset, in pixels. */
+export declare const VIEWPORT_SNAP_TOLERANCE = 8;
+/**
+ * The named widths, as numbers.
+ *
+ * Common CSS breakpoints plus the two phone widths that actually differ from
+ * them. Rendered as the "Width" group in the canvas tools menu, like the zoom
+ * chooser next to it.
+ */
+export declare const VIEWPORT_SNAPS: readonly number[];
+/**
+ * `width` brought inside the legal range and onto a whole pixel.
+ *
+ * Lives next to the bounds, not the canvas snapping, because the service uses
+ * it to keep stored and programmatic widths legal and should not import from
+ * the canvas UI folder.
+ *
+ * Rounded, not truncated: the value is shown as a label on the canvas, and
+ * `389.6 px` during a drag looks like a rendering bug.
+ */
+export declare function clampViewportWidth(width: number): number;
+//# sourceMappingURL=viewport.type.d.ts.map

package/dist/shared/viewport.type.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"viewport.type.d.ts","sourceRoot":"","sources":["../../src/shared/viewport.type.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH;;;;;;;GAOG;AACH,eAAO,MAAM,YAAY,MAAM,CAAC;AAEhC,gHAAgH;AAChH,eAAO,MAAM,YAAY,OAAO,CAAC;AAEjC,sEAAsE;AACtE,eAAO,MAAM,gBAAgB,MAAM,CAAC;AAEpC,0EAA0E;AAC1E,eAAO,MAAM,uBAAuB,IAAI,CAAC;AAEzC;;;;;;GAMG;AACH,eAAO,MAAM,cAAc,EAAE,SAAS,MAAM,EAAoC,CAAC;AAEjF;;;;;;;;;GASG;AACH,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAExD"}

package/dist/shared/viewport.type.js

@@ -0,0 +1,44 @@
+/**
+ * The canvas viewport: one nullable number, not a device list.
+ *
+ * The tool is for finding where a layout breaks, so the presets are plain
+ * widths without device names. A device name would suggest a simulation; the
+ * constraint only narrows the box. Media queries still read the real browser
+ * viewport; only `@container` rules respond.
+ */
+/**
+ * The narrowest the constraint will go.
+ *
+ * Below any real device. The presets cover the widths people design against;
+ * the floor lets a drag go past them to find where a layout breaks. A floor at
+ * the narrowest real phone would hide that point for the components most worth
+ * checking.
+ */
+export const VIEWPORT_MIN = 100;
+/** Wide enough for a desktop breakpoint, short of the point where the stage scrolls on any realistic screen. */
+export const VIEWPORT_MAX = 1600;
+/** Where the toggle lands when no width has been set this session. */
+export const VIEWPORT_DEFAULT = 390;
+/** How near a drag has to come before it rests on a preset, in pixels. */
+export const VIEWPORT_SNAP_TOLERANCE = 8;
+/**
+ * The named widths, as numbers.
+ *
+ * Common CSS breakpoints plus the two phone widths that actually differ from
+ * them. Rendered as the "Width" group in the canvas tools menu, like the zoom
+ * chooser next to it.
+ */
+export const VIEWPORT_SNAPS = [320, 390, 480, 640, 768, 1024];
+/**
+ * `width` brought inside the legal range and onto a whole pixel.
+ *
+ * Lives next to the bounds, not the canvas snapping, because the service uses
+ * it to keep stored and programmatic widths legal and should not import from
+ * the canvas UI folder.
+ *
+ * Rounded, not truncated: the value is shown as a label on the canvas, and
+ * `389.6 px` during a drag looks like a rendering bug.
+ */
+export function clampViewportWidth(width) {
+    return Math.round(Math.max(VIEWPORT_MIN, Math.min(VIEWPORT_MAX, width)));
+}

package/dist/transformer/index.d.ts

@@ -1,3 +1,3 @@
-export { createShowcaseStripTransformer, stripShowcaseDecorators, } from './showcase-strip.transformer.js';
-export { stripShowcaseFromDirectory, type StripResult, } from './strip-directory.js';
+export { createShowcaseStripTransformer, stripShowcaseDecorators } from './showcase-strip.transformer.js';
+export { type StripResult, stripShowcaseFromDirectory } from './strip-directory.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/transformer/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/transformer/index.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,8BAA8B,EAC9B,uBAAuB,GACxB,MAAM,iCAAiC,CAAC;AACzC,OAAO,EACL,0BAA0B,EAC1B,KAAK,WAAW,GACjB,MAAM,sBAAsB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/transformer/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,8BAA8B,EAAE,uBAAuB,EAAE,MAAM,iCAAiC,CAAC;AAC1G,OAAO,EAAE,KAAK,WAAW,EAAE,0BAA0B,EAAE,MAAM,sBAAsB,CAAC"}

package/dist/transformer/index.js

@@ -1,2 +1,2 @@
-export { createShowcaseStripTransformer, stripShowcaseDecorators, } from './showcase-strip.transformer.js';
-export { stripShowcaseFromDirectory, } from './strip-directory.js';
+export { createShowcaseStripTransformer, stripShowcaseDecorators } from './showcase-strip.transformer.js';
+export { stripShowcaseFromDirectory } from './strip-directory.js';

package/dist/transformer/showcase-strip.transformer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"showcase-strip.transformer.d.ts","sourceRoot":"","sources":["../../src/transformer/showcase-strip.transformer.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,YAAY,CAAC;AAoN5B,wBAAgB,8BAA8B,IAAI,EAAE,CAAC,kBAAkB,CAAC,EAAE,CAAC,UAAU,CAAC,CA8CrF;AA6BD,wBAAgB,uBAAuB,CACrC,MAAM,EAAE,MAAM,EACd,QAAQ,SAAY,GACnB,MAAM,CAgCR"}
+{"version":3,"file":"showcase-strip.transformer.d.ts","sourceRoot":"","sources":["../../src/transformer/showcase-strip.transformer.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,YAAY,CAAC;AAqK5B,wBAAgB,8BAA8B,IAAI,EAAE,CAAC,kBAAkB,CAAC,EAAE,CAAC,UAAU,CAAC,CA2CrF;AAyBD,wBAAgB,uBAAuB,CAAC,MAAM,EAAE,MAAM,EAAE,QAAQ,SAAY,GAAG,MAAM,CAyBpF"}

package/dist/transformer/showcase-strip.transformer.js

@@ -4,9 +4,7 @@ function isShowcaseModule(specifier) {
     return SHOWCASE_MODULE_PREFIXES.some((prefix) => specifier === prefix || specifier.startsWith(prefix + '/'));
 }
 function isShowcaseCall(expr, names) {
-    return (ts.isCallExpression(expr) &&
-        ts.isIdentifier(expr.expression) &&
-        names.has(expr.expression.text));
+    return ts.isCallExpression(expr) && ts.isIdentifier(expr.expression) && names.has(expr.expression.text);
 }
 function isLoweredShowcaseCall(expr, names) {
     if (!ts.isCallExpression(expr))
@@ -15,21 +13,17 @@ function isLoweredShowcaseCall(expr, names) {
 }
 function tryHandleDecorateStatement(stmt, names, factory) {
     const expr = stmt.expression;
-    if (!ts.isBinaryExpression(expr) ||
-        expr.operatorToken.kind !== ts.SyntaxKind.EqualsToken) {
+    if (!ts.isBinaryExpression(expr) || expr.operatorToken.kind !== ts.SyntaxKind.EqualsToken) {
         return undefined;
     }
     const chain = [];
     let current = expr;
-    while (ts.isBinaryExpression(current) &&
-        current.operatorToken.kind === ts.SyntaxKind.EqualsToken) {
+    while (ts.isBinaryExpression(current) && current.operatorToken.kind === ts.SyntaxKind.EqualsToken) {
         chain.push(current);
         current = current.right;
     }
     const rhs = current;
-    if (!ts.isCallExpression(rhs) ||
-        !ts.isIdentifier(rhs.expression) ||
-        rhs.expression.text !== '__decorate') {
+    if (!ts.isCallExpression(rhs) || !ts.isIdentifier(rhs.expression) || rhs.expression.text !== '__decorate') {
         return undefined;
     }
     const args = rhs.arguments;
@@ -55,9 +49,7 @@ function tryHandleDecorateStatement(stmt, names, factory) {
     return { action: 'replace', statement: newStmt };
 }
 function isShowcaseDecorator(d, names) {
-    return (ts.isCallExpression(d.expression) &&
-        ts.isIdentifier(d.expression.expression) &&
-        names.has(d.expression.expression.text));
+    return ts.isCallExpression(d.expression) && ts.isIdentifier(d.expression.expression) && names.has(d.expression.expression.text);
 }
 function stripNativeDecorators(node, names, factory) {
     const decorators = ts.getDecorators(node);
@@ -128,8 +120,7 @@ export function createShowcaseStripTransformer() {
                         continue;
                     const decorateResult = tryHandleDecorateStatement(stmt, names, factory);
                     if (decorateResult) {
-                        if (decorateResult.action === 'replace' &&
-                            decorateResult.statement) {
+                        if (decorateResult.action === 'replace' && decorateResult.statement) {
                             filtered.push(decorateResult.statement);
                         }
                         continue;
@@ -177,7 +168,7 @@ export function stripShowcaseDecorators(source, fileName = 'file.ts') {
     const leak = findShowcaseLeak(audited, importInfo.localNames);
     if (leak) {
         throw new Error(`[ng-prism] Showcase reference '${leak.name}' left in output after stripping at ${fileName}:${leak.line}. ` +
-            `The Showcase import was removed but a reference remains — this would cause a ReferenceError at runtime. ` +
+            `The Showcase import was removed but a reference remains, which would cause a ReferenceError at runtime. ` +
             `This is a transformer bug; please report the input source.`);
     }
     return output;

package/dist/transformer/strip-directory.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"strip-directory.d.ts","sourceRoot":"","sources":["../../src/transformer/strip-directory.ts"],"names":[],"mappings":"AAIA,MAAM,WAAW,WAAW;IAC1B,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,MAAM,CAAC;CACvB;AAID,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,CAAC,CAkBlF"}
+{"version":3,"file":"strip-directory.d.ts","sourceRoot":"","sources":["../../src/transformer/strip-directory.ts"],"names":[],"mappings":"AAIA,MAAM,WAAW,WAAW;IACxB,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,MAAM,CAAC;CACzB;AAID,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,CAAC,CAiBlF"}

package/dist/transformer/strip-directory.js

@@ -1,12 +1,10 @@
 import { readdir, readFile, writeFile } from 'node:fs/promises';
-import { join, extname } from 'node:path';
+import { extname, join } from 'node:path';
 import { stripShowcaseDecorators } from './showcase-strip.transformer.js';
 const JS_EXTENSIONS = new Set(['.js', '.mjs']);
 export async function stripShowcaseFromDirectory(dir) {
     const entries = await readdir(dir, { recursive: true });
-    const files = entries
-        .filter((entry) => JS_EXTENSIONS.has(extname(entry)))
-        .map((entry) => join(dir, entry));
+    const files = entries.filter((entry) => JS_EXTENSIONS.has(extname(entry))).map((entry) => join(dir, entry));
     let strippedFiles = 0;
     for (const file of files) {
         const source = await readFile(file, 'utf-8');

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ng-prism/core",
-  "version": "22.2.1",
-  "description": "ng-prism — the Angular-native Storybook alternative. Lightweight component showcase with @Showcase decorator, no story files needed.",
+  "version": "22.4.0",
+  "description": "ng-prism: the Angular-native Storybook alternative. Lightweight component showcase with @Showcase decorator, no story files needed.",
   "keywords": [
     "ng-prism",
     "angular",
@@ -76,6 +76,7 @@
   "peerDependencies": {
     "@angular/core": ">=20.0.0",
     "@angular/common": ">=20.0.0",
+    "@angular/compiler": ">=20.0.0",
     "@angular-devkit/architect": ">=0.2000.0",
     "@angular-devkit/core": ">=20.0.0",
     "@angular-devkit/schematics": ">=20.0.0",
@@ -92,7 +93,9 @@
     }
   },
   "dependencies": {
+    "axe-core": "^4.11.1",
     "chokidar": "^5.0.0",
+    "jsonc-parser": "^3.3.1",
     "tslib": "^2.3.0"
   },
   "repository": {

package/schematics/collection.json

@@ -1,10 +1,10 @@
 {
-  "$schema": "../node_modules/@angular-devkit/schematics/collection-schema.json",
-  "schematics": {
-    "ng-add": {
-      "description": "Set up ng-prism in an Angular workspace",
-      "factory": "../dist/schematics/ng-add/index#ngAdd",
-      "schema": "./ng-add/schema.json"
+    "$schema": "../node_modules/@angular-devkit/schematics/collection-schema.json",
+    "schematics": {
+        "ng-add": {
+            "description": "Set up ng-prism in an Angular workspace",
+            "factory": "../dist/schematics/ng-add/index#ngAdd",
+            "schema": "./ng-add/schema.json"
+        }
     }
-  }
 }

package/schematics/migrations.json

@@ -1,15 +1,15 @@
 {
-  "$schema": "../node_modules/@angular-devkit/schematics/collection-schema.json",
-  "schematics": {
-    "migration-v22-manifest-cache": {
-      "version": "22.0.0-beta.0",
-      "description": "Move generated prism-manifest.ts into <workspaceRoot>/ng-prism-cache/<prismProject>/ and resolve it via a wildcard tsconfig path mapping.",
-      "factory": "../dist/schematics/migrations/v21-13-manifest-cache/index#migrate"
-    },
-    "migration-v22-cache-dir-rename": {
-      "version": "22.0.0-beta.4",
-      "description": "Rename the manifest cache directory from .ng-prism/ to ng-prism-cache/. The dot-prefixed name was silently excluded from @angular/build's watcher (hardcoded **/.*/** ignore pattern), so @Showcase decorator edits never triggered an HMR / reload.",
-      "factory": "../dist/schematics/migrations/v22-0-cache-dir-rename/index#migrate"
+    "$schema": "../node_modules/@angular-devkit/schematics/collection-schema.json",
+    "schematics": {
+        "migration-v22-manifest-cache": {
+            "version": "22.0.0-beta.0",
+            "description": "Move generated prism-manifest.ts into <workspaceRoot>/ng-prism-cache/<prismProject>/ and resolve it via a wildcard tsconfig path mapping.",
+            "factory": "../dist/schematics/migrations/v21-13-manifest-cache/index#migrate"
+        },
+        "migration-v22-cache-dir-rename": {
+            "version": "22.0.0-beta.4",
+            "description": "Rename the manifest cache directory from .ng-prism/ to ng-prism-cache/. The dot-prefixed name was silently excluded from @angular/build's watcher (hardcoded **/.*/** ignore pattern), so @Showcase decorator edits never triggered an HMR / reload.",
+            "factory": "../dist/schematics/migrations/v22-0-cache-dir-rename/index#migrate"
+        }
     }
-  }
 }

package/schematics/ng-add/schema.json

@@ -1,25 +1,25 @@
 {
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "ng-prism ng-add Schematic",
-  "description": "Set up ng-prism in an Angular workspace",
-  "type": "object",
-  "properties": {
-    "project": {
-      "type": "string",
-      "description": "The library project to set up ng-prism for",
-      "x-prompt": "Which library project should ng-prism showcase?"
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "title": "ng-prism ng-add Schematic",
+    "description": "Set up ng-prism in an Angular workspace",
+    "type": "object",
+    "properties": {
+        "project": {
+            "type": "string",
+            "description": "The library project to set up ng-prism for",
+            "x-prompt": "Which library project should ng-prism showcase?"
+        },
+        "port": {
+            "type": "number",
+            "default": 4400,
+            "description": "Dev server port for the Prism styleguide"
+        },
+        "zoneless": {
+            "type": "boolean",
+            "default": false,
+            "description": "Use zoneless change detection (no zone.js polyfill)"
+        }
     },
-    "port": {
-      "type": "number",
-      "default": 4400,
-      "description": "Dev server port for the Prism styleguide"
-    },
-    "zoneless": {
-      "type": "boolean",
-      "default": false,
-      "description": "Use zoneless change detection (no zone.js polyfill)"
-    }
-  },
-  "required": ["project"],
-  "additionalProperties": false
+    "required": ["project"],
+    "additionalProperties": false
 }