@cratis/scene.primereact 1.0.0 → 2.0.0

package/dist/cjs/screen/PrimeSummary.js

@@ -11,35 +11,59 @@ var properties = require('../properties.js');
  * Rendered as a description list inside a card. A description list is the correct element for
  * label/value pairs and gets the pairing across to a screen reader for free, which a grid of `div`s does
  * not.
+ *
+ * PrimeReact 11 made `Card` compositional, so the v10 `<Card title=...>` form is assembled here from
+ * `Card.Root` / `Card.Body` / `Card.Caption` / `Card.Title` / `Card.Content` instead.
+ *
+ * The nesting matters and is easy to get wrong. `Card.Body` is the part that carries the padding - it is
+ * the only one of them the preset gives a `padding` token - so everything visible has to sit inside it.
+ * A title placed in a `Card.Header` instead renders flush to the card edge with no styling at all,
+ * because `header` is not a themed part: the preset's `card` tokens are exactly `root`, `body`,
+ * `caption`, `title` and `subtitle`, and `p-card-header` is v11's slot for a media image above the body.
+ *
+ * The caption is rendered only when a title was authored. v10 collapsed an absent `title` to nothing, and
+ * an empty `Card.Caption` still reserves its own gap, which would leave a stray band above a summary that
+ * simply has no heading.
  */ function PrimeSummary({ element, slots }) {
     const items = properties.recordArrayProperty(element, 'items');
-    return /*#__PURE__*/ jsxRuntime.jsxs(card.Card, {
+    const title = properties.stringProperty(element, 'title');
+    return /*#__PURE__*/ jsxRuntime.jsx(card.Card.Root, {
         "data-scene-id": element.id,
-        title: properties.stringProperty(element, 'title'),
-        children: [
-            /*#__PURE__*/ jsxRuntime.jsx("dl", {
-                className: "grid grid-cols-2 gap-2",
-                children: items.map((item, index)=>/*#__PURE__*/ jsxRuntime.jsxs("div", {
-                        className: "flex flex-col",
-                        children: [
-                            /*#__PURE__*/ jsxRuntime.jsx("dt", {
-                                className: "text-sm",
-                                style: {
-                                    color: 'var(--scene-text-muted-color)'
-                                },
-                                children: String(item.label ?? '')
-                            }),
-                            /*#__PURE__*/ jsxRuntime.jsx("dd", {
-                                style: {
-                                    color: 'var(--scene-text-color)'
-                                },
-                                children: String(item.value ?? '')
-                            })
-                        ]
-                    }, index))
-            }),
-            slots.content
-        ]
+        children: /*#__PURE__*/ jsxRuntime.jsxs(card.Card.Body, {
+            children: [
+                title !== undefined && /*#__PURE__*/ jsxRuntime.jsx(card.Card.Caption, {
+                    children: /*#__PURE__*/ jsxRuntime.jsx(card.Card.Title, {
+                        children: title
+                    })
+                }),
+                /*#__PURE__*/ jsxRuntime.jsxs(card.Card.Content, {
+                    children: [
+                        /*#__PURE__*/ jsxRuntime.jsx("dl", {
+                            className: "grid grid-cols-2 gap-2",
+                            children: items.map((item, index)=>/*#__PURE__*/ jsxRuntime.jsxs("div", {
+                                    className: "flex flex-col",
+                                    children: [
+                                        /*#__PURE__*/ jsxRuntime.jsx("dt", {
+                                            className: "text-sm",
+                                            style: {
+                                                color: 'var(--scene-text-muted-color)'
+                                            },
+                                            children: String(item.label ?? '')
+                                        }),
+                                        /*#__PURE__*/ jsxRuntime.jsx("dd", {
+                                            style: {
+                                                color: 'var(--scene-text-color)'
+                                            },
+                                            children: String(item.value ?? '')
+                                        })
+                                    ]
+                                }, index))
+                        }),
+                        slots.content
+                    ]
+                })
+            ]
+        })
     });
 }
 

package/dist/cjs/screen/PrimeSummary.js.map

@@ -1 +1 @@
-{"version":3,"file":"PrimeSummary.js","sources":["../../../screen/PrimeSummary.tsx"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Card } from 'primereact/card';\nimport { RegisteredComponentProps } from '@cratis/scene.react';\nimport { recordArrayProperty, stringProperty } from '../properties';\n\n/**\n * The `PrimeReact:summary` component - one of Screenplay's screen directives: the headline facts about\n * one thing.\n *\n * Rendered as a description list inside a card. A description list is the correct element for\n * label/value pairs and gets the pairing across to a screen reader for free, which a grid of `div`s does\n * not.\n */\nexport function PrimeSummary({ element, slots }: RegisteredComponentProps) {\n    const items = recordArrayProperty(element, 'items');\n    return (\n        <Card data-scene-id={element.id} title={stringProperty(element, 'title')}>\n            <dl className='grid grid-cols-2 gap-2'>\n                {items.map((item, index) => (\n                    <div key={index} className='flex flex-col'>\n                        <dt className='text-sm' style={{ color: 'var(--scene-text-muted-color)' }}>\n                            {String(item.label ?? '')}\n                        </dt>\n                        <dd style={{ color: 'var(--scene-text-color)' }}>{String(item.value ?? '')}</dd>\n                    </div>\n                ))}\n            </dl>\n            {slots.content}\n        </Card>\n    );\n}\n"],"names":["PrimeSummary","element","slots","items","recordArrayProperty","_jsxs","Card","data-scene-id","id","title","stringProperty","_jsx","dl","className","map","item","index","div","dt","style","color","String","label","dd","value","content"],"mappings":";;;;;;AAOA;;;;;;;AAOC,IACM,SAASA,YAAAA,CAAa,EAAEC,OAAO,EAAEC,KAAK,EAA4B,EAAA;IACrE,MAAMC,KAAAA,GAAQC,+BAAoBH,OAAAA,EAAS,OAAA,CAAA;AAC3C,IAAA,qBACII,eAAA,CAACC,SAAAA,EAAAA;AAAKC,QAAAA,eAAAA,EAAeN,QAAQO,EAAE;AAAEC,QAAAA,KAAAA,EAAOC,0BAAeT,OAAAA,EAAS,OAAA,CAAA;;0BAC5DU,cAAA,CAACC,IAAAA,EAAAA;gBAAGC,SAAAA,EAAU,wBAAA;AACTV,gBAAAA,QAAAA,EAAAA,KAAAA,CAAMW,GAAG,CAAC,CAACC,IAAAA,EAAMC,sBACdX,eAAA,CAACY,KAAAA,EAAAA;wBAAgBJ,SAAAA,EAAU,eAAA;;0CACvBF,cAAA,CAACO,IAAAA,EAAAA;gCAAGL,SAAAA,EAAU,SAAA;gCAAUM,KAAAA,EAAO;oCAAEC,KAAAA,EAAO;AAAgC,iCAAA;0CACnEC,MAAAA,CAAON,IAAAA,CAAKO,KAAK,IAAI,EAAA;;0CAE1BX,cAAA,CAACY,IAAAA,EAAAA;gCAAGJ,KAAAA,EAAO;oCAAEC,KAAAA,EAAO;AAA0B,iCAAA;0CAAIC,MAAAA,CAAON,IAAAA,CAAKS,KAAK,IAAI,EAAA;;;AAJjER,qBAAAA,EAAAA,KAAAA,CAAAA;;AAQjBd,YAAAA,KAAAA,CAAMuB;;;AAGnB;;;;"}
+{"version":3,"file":"PrimeSummary.js","sources":["../../../screen/PrimeSummary.tsx"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Card } from 'primereact/card';\nimport { RegisteredComponentProps } from '@cratis/scene.react';\nimport { recordArrayProperty, stringProperty } from '../properties';\n\n/**\n * The `PrimeReact:summary` component - one of Screenplay's screen directives: the headline facts about\n * one thing.\n *\n * Rendered as a description list inside a card. A description list is the correct element for\n * label/value pairs and gets the pairing across to a screen reader for free, which a grid of `div`s does\n * not.\n *\n * PrimeReact 11 made `Card` compositional, so the v10 `<Card title=...>` form is assembled here from\n * `Card.Root` / `Card.Body` / `Card.Caption` / `Card.Title` / `Card.Content` instead.\n *\n * The nesting matters and is easy to get wrong. `Card.Body` is the part that carries the padding - it is\n * the only one of them the preset gives a `padding` token - so everything visible has to sit inside it.\n * A title placed in a `Card.Header` instead renders flush to the card edge with no styling at all,\n * because `header` is not a themed part: the preset's `card` tokens are exactly `root`, `body`,\n * `caption`, `title` and `subtitle`, and `p-card-header` is v11's slot for a media image above the body.\n *\n * The caption is rendered only when a title was authored. v10 collapsed an absent `title` to nothing, and\n * an empty `Card.Caption` still reserves its own gap, which would leave a stray band above a summary that\n * simply has no heading.\n */\nexport function PrimeSummary({ element, slots }: RegisteredComponentProps) {\n    const items = recordArrayProperty(element, 'items');\n    const title = stringProperty(element, 'title');\n    return (\n        <Card.Root data-scene-id={element.id}>\n            <Card.Body>\n                {title !== undefined && (\n                    <Card.Caption>\n                        <Card.Title>{title}</Card.Title>\n                    </Card.Caption>\n                )}\n                <Card.Content>\n                <dl className='grid grid-cols-2 gap-2'>\n                    {items.map((item, index) => (\n                        <div key={index} className='flex flex-col'>\n                            <dt className='text-sm' style={{ color: 'var(--scene-text-muted-color)' }}>\n                                {String(item.label ?? '')}\n                            </dt>\n                            <dd style={{ color: 'var(--scene-text-color)' }}>{String(item.value ?? '')}</dd>\n                        </div>\n                    ))}\n                </dl>\n                    {slots.content}\n                </Card.Content>\n            </Card.Body>\n        </Card.Root>\n    );\n}\n"],"names":["PrimeSummary","element","slots","items","recordArrayProperty","title","stringProperty","_jsx","Card","Root","data-scene-id","id","_jsxs","Body","undefined","Caption","Title","Content","dl","className","map","item","index","div","dt","style","color","String","label","dd","value","content"],"mappings":";;;;;;AAOA;;;;;;;;;;;;;;;;;;;;AAoBC,IACM,SAASA,YAAAA,CAAa,EAAEC,OAAO,EAAEC,KAAK,EAA4B,EAAA;IACrE,MAAMC,KAAAA,GAAQC,+BAAoBH,OAAAA,EAAS,OAAA,CAAA;IAC3C,MAAMI,KAAAA,GAAQC,0BAAeL,OAAAA,EAAS,OAAA,CAAA;IACtC,qBACIM,cAAA,CAACC,UAAKC,IAAI,EAAA;AAACC,QAAAA,eAAAA,EAAeT,QAAQU,EAAE;gCAChCC,eAAA,CAACJ,UAAKK,IAAI,EAAA;;gBACLR,KAAAA,KAAUS,SAAAA,kBACPP,cAAA,CAACC,SAAAA,CAAKO,OAAO,EAAA;4CACTR,cAAA,CAACC,UAAKQ,KAAK,EAAA;AAAEX,wBAAAA,QAAAA,EAAAA;;;AAGrB,8BAAAO,eAAA,CAACJ,UAAKS,OAAO,EAAA;;sCACbV,cAAA,CAACW,IAAAA,EAAAA;4BAAGC,SAAAA,EAAU,wBAAA;AACThB,4BAAAA,QAAAA,EAAAA,KAAAA,CAAMiB,GAAG,CAAC,CAACC,IAAAA,EAAMC,sBACdV,eAAA,CAACW,KAAAA,EAAAA;oCAAgBJ,SAAAA,EAAU,eAAA;;sDACvBZ,cAAA,CAACiB,IAAAA,EAAAA;4CAAGL,SAAAA,EAAU,SAAA;4CAAUM,KAAAA,EAAO;gDAAEC,KAAAA,EAAO;AAAgC,6CAAA;sDACnEC,MAAAA,CAAON,IAAAA,CAAKO,KAAK,IAAI,EAAA;;sDAE1BrB,cAAA,CAACsB,IAAAA,EAAAA;4CAAGJ,KAAAA,EAAO;gDAAEC,KAAAA,EAAO;AAA0B,6CAAA;sDAAIC,MAAAA,CAAON,IAAAA,CAAKS,KAAK,IAAI,EAAA;;;AAJjER,iCAAAA,EAAAA,KAAAA,CAAAA;;AAQbpB,wBAAAA,KAAAA,CAAM6B;;;;;;AAK3B;;;;"}

package/dist/cjs/theme/PrimeReactThemeFamily.js

@@ -0,0 +1,34 @@
+'use strict';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The `@primeuix/themes` preset families a PrimeReact 11 theme can be built on.
+ *
+ * PrimeReact 10 had no concept like this: a theme was a folder name and a compiled stylesheet, and the
+ * family it belonged to was a naming convention rather than anything the code could act on. In v11 the
+ * family is the actual unit of design - a JavaScript preset object supplied to `PrimeReactProvider` -
+ * and a Scene theme is that preset plus an accent color. Making it an enum rather than a string means a
+ * theme cannot name a family that does not exist, and `primeReactThemePreset` gets an exhaustive
+ * `switch` the compiler checks when PrimeTek adds a fifth family.
+ */ var PrimeReactThemeFamily = /*#__PURE__*/ function(PrimeReactThemeFamily) {
+    /**
+     * Aura - PrimeTek's flagship design language for v11, and the one their own documentation defaults
+     * to. Softer radii and a lower-contrast surface ramp than Lara.
+     */ PrimeReactThemeFamily["Aura"] = "aura";
+    /**
+     * Lara - the family Scene shipped throughout PrimeReact 10. Carried forward so an application
+     * upgrading from v10 can keep a recognisably similar look.
+     */ PrimeReactThemeFamily["Lara"] = "lara";
+    /**
+     * Nora - tighter spacing, squarer corners and heavier borders. The most compact of the four.
+     */ PrimeReactThemeFamily["Nora"] = "nora";
+    /**
+     * Material - PrimeTek's reading of Material Design, and the nearest thing v11 has to the v10
+     * `md-*` and `mdc-*` themes.
+     */ PrimeReactThemeFamily["Material"] = "material";
+    return PrimeReactThemeFamily;
+}({});
+
+exports.PrimeReactThemeFamily = PrimeReactThemeFamily;
+//# sourceMappingURL=PrimeReactThemeFamily.js.map

package/dist/cjs/theme/PrimeReactThemeFamily.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PrimeReactThemeFamily.js","sources":["../../../theme/PrimeReactThemeFamily.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\n/**\n * The `@primeuix/themes` preset families a PrimeReact 11 theme can be built on.\n *\n * PrimeReact 10 had no concept like this: a theme was a folder name and a compiled stylesheet, and the\n * family it belonged to was a naming convention rather than anything the code could act on. In v11 the\n * family is the actual unit of design - a JavaScript preset object supplied to `PrimeReactProvider` -\n * and a Scene theme is that preset plus an accent color. Making it an enum rather than a string means a\n * theme cannot name a family that does not exist, and `primeReactThemePreset` gets an exhaustive\n * `switch` the compiler checks when PrimeTek adds a fifth family.\n */\nexport enum PrimeReactThemeFamily {\n    /**\n     * Aura - PrimeTek's flagship design language for v11, and the one their own documentation defaults\n     * to. Softer radii and a lower-contrast surface ramp than Lara.\n     */\n    Aura = 'aura',\n\n    /**\n     * Lara - the family Scene shipped throughout PrimeReact 10. Carried forward so an application\n     * upgrading from v10 can keep a recognisably similar look.\n     */\n    Lara = 'lara',\n\n    /**\n     * Nora - tighter spacing, squarer corners and heavier borders. The most compact of the four.\n     */\n    Nora = 'nora',\n\n    /**\n     * Material - PrimeTek's reading of Material Design, and the nearest thing v11 has to the v10\n     * `md-*` and `mdc-*` themes.\n     */\n    Material = 'material',\n}\n"],"names":["PrimeReactThemeFamily"],"mappings":";;AAAA;AACA;AAEA;;;;;;;;;IAUO,IAAKA,qBAAAA,iBAAAA,SAAAA,qBAAAA,EAAAA;AACR;;;AAGC,QAAA,qBAAA,CAAA,MAAA,CAAA,GAAA,MAAA;AAGD;;;AAGC,QAAA,qBAAA,CAAA,MAAA,CAAA,GAAA,MAAA;AAGD;;AAEC,QAAA,qBAAA,CAAA,MAAA,CAAA,GAAA,MAAA;AAGD;;;AAGC,QAAA,qBAAA,CAAA,UAAA,CAAA,GAAA,UAAA;AArBOA,IAAAA,OAAAA,qBAAAA;AAuBX,CAAA,CAAA,EAAA;;;;"}

package/dist/cjs/theme/primeReactThemePreset.js

@@ -0,0 +1,73 @@
+'use strict';
+
+var themes = require('@primeuix/themes');
+var Aura = require('@primeuix/themes/aura');
+var Lara = require('@primeuix/themes/lara');
+var Material = require('@primeuix/themes/material');
+var Nora = require('@primeuix/themes/nora');
+var PrimeReactThemeFamily = require('./PrimeReactThemeFamily.js');
+var themePresets = require('./themePresets.js');
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The base preset object for each family.
+ *
+ * These are PrimeTek's own preset exports, untouched. The accent binding in
+ * {@link primeReactThemePreset} is applied on top with `definePreset`, which merges rather than mutates -
+ * important, because these objects are module singletons and two themes tinted differently must not
+ * fight over one shared object.
+ */ const basePresets = {
+    [PrimeReactThemeFamily.PrimeReactThemeFamily.Aura]: Aura,
+    [PrimeReactThemeFamily.PrimeReactThemeFamily.Lara]: Lara,
+    [PrimeReactThemeFamily.PrimeReactThemeFamily.Nora]: Nora,
+    [PrimeReactThemeFamily.PrimeReactThemeFamily.Material]: Material
+};
+/**
+ * Presets are built once per theme name and reused.
+ *
+ * `definePreset` deep-merges, so calling it per render would produce a new object every time - and
+ * `PrimeReactProvider` treats a new preset identity as a theme change, which re-emits every `--p-*`
+ * custom property. Caching keeps switching themes cheap and, more importantly, keeps *not* switching
+ * free.
+ */ const presetCache = new Map();
+/**
+ * Resolves one of this package's themes to the `@primeuix/themes` preset that renders it.
+ *
+ * This is what replaced `primeReactThemeStylesheet` in the PrimeReact 11 port, and the change is the
+ * whole shape of theming in v11 in one function. A v10 theme was a *file*: the question was which URL to
+ * load, the answer was a string, and applying it meant swapping a `<link>`. A v11 theme is an *object*:
+ * the question is which preset to hand `PrimeReactProvider`, the answer is a value, and applying it
+ * means re-rendering a provider. Nothing is fetched, so there is no unstyled flash on switch and no way
+ * for a theme to 404.
+ *
+ * The accent is bound by overriding the preset's `primary` scale with a primitive color ramp the preset
+ * already ships - so `lara-light-teal` is genuinely Lara with Lara's own teal, not an approximation
+ * mixed here.
+ *
+ * @param themeName The theme name, as it appears in {@link themePresets}.
+ * @returns The preset, or `undefined` when this package ships no theme by that name. `undefined` rather
+ * than a default preset, because silently theming a screen as something other than what was asked for is
+ * harder to notice than nothing happening.
+ */ function primeReactThemePreset(themeName) {
+    const cached = presetCache.get(themeName);
+    if (cached !== undefined) return cached;
+    const preset = themePresets.themePresets.find((candidate)=>candidate.name === themeName);
+    if (preset === undefined) return undefined;
+    const base = basePresets[preset.family];
+    // The ramp is looked up by name, so its type has to be widened to index the primitives and then
+    // narrowed again for `definePreset`. `ColorScale` is the shape every primitive color in a preset has -
+    // the 50..950 steps - and `primaryColor` is only ever one of those names, guaranteed by the catalog.
+    const primitives = base.primitive;
+    const ramp = primitives[preset.primaryColor];
+    const built = themes.definePreset(base, {
+        semantic: {
+            primary: ramp
+        }
+    });
+    presetCache.set(themeName, built);
+    return built;
+}
+
+exports.primeReactThemePreset = primeReactThemePreset;
+//# sourceMappingURL=primeReactThemePreset.js.map

package/dist/cjs/theme/primeReactThemePreset.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"primeReactThemePreset.js","sources":["../../../theme/primeReactThemePreset.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { definePreset } from '@primeuix/themes';\nimport Aura from '@primeuix/themes/aura';\nimport Lara from '@primeuix/themes/lara';\nimport Material from '@primeuix/themes/material';\nimport Nora from '@primeuix/themes/nora';\nimport { PrimeReactThemeFamily } from './PrimeReactThemeFamily';\nimport { themePresets } from './themePresets';\n\n/**\n * A `@primeuix/themes` preset, as `PrimeReactProvider` wants it.\n *\n * `@primeuix/themes` types this as `Preset`, but the type is generic over the preset's own token shape\n * and the four families do not share one instantiation, so naming the union here rather than importing\n * `Preset` keeps the call sites free of casts.\n */\nexport type PrimeReactPreset = typeof Aura | typeof Lara | typeof Nora | typeof Material;\n\n/**\n * The base preset object for each family.\n *\n * These are PrimeTek's own preset exports, untouched. The accent binding in\n * {@link primeReactThemePreset} is applied on top with `definePreset`, which merges rather than mutates -\n * important, because these objects are module singletons and two themes tinted differently must not\n * fight over one shared object.\n */\nconst basePresets: Record<PrimeReactThemeFamily, PrimeReactPreset> = {\n    [PrimeReactThemeFamily.Aura]: Aura,\n    [PrimeReactThemeFamily.Lara]: Lara,\n    [PrimeReactThemeFamily.Nora]: Nora,\n    [PrimeReactThemeFamily.Material]: Material,\n};\n\n/**\n * Presets are built once per theme name and reused.\n *\n * `definePreset` deep-merges, so calling it per render would produce a new object every time - and\n * `PrimeReactProvider` treats a new preset identity as a theme change, which re-emits every `--p-*`\n * custom property. Caching keeps switching themes cheap and, more importantly, keeps *not* switching\n * free.\n */\nconst presetCache = new Map<string, PrimeReactPreset>();\n\n/**\n * Resolves one of this package's themes to the `@primeuix/themes` preset that renders it.\n *\n * This is what replaced `primeReactThemeStylesheet` in the PrimeReact 11 port, and the change is the\n * whole shape of theming in v11 in one function. A v10 theme was a *file*: the question was which URL to\n * load, the answer was a string, and applying it meant swapping a `<link>`. A v11 theme is an *object*:\n * the question is which preset to hand `PrimeReactProvider`, the answer is a value, and applying it\n * means re-rendering a provider. Nothing is fetched, so there is no unstyled flash on switch and no way\n * for a theme to 404.\n *\n * The accent is bound by overriding the preset's `primary` scale with a primitive color ramp the preset\n * already ships - so `lara-light-teal` is genuinely Lara with Lara's own teal, not an approximation\n * mixed here.\n *\n * @param themeName The theme name, as it appears in {@link themePresets}.\n * @returns The preset, or `undefined` when this package ships no theme by that name. `undefined` rather\n * than a default preset, because silently theming a screen as something other than what was asked for is\n * harder to notice than nothing happening.\n */\nexport function primeReactThemePreset(themeName: string): PrimeReactPreset | undefined {\n    const cached = presetCache.get(themeName);\n    if (cached !== undefined) return cached;\n\n    const preset = themePresets.find((candidate) => candidate.name === themeName);\n    if (preset === undefined) return undefined;\n\n    const base = basePresets[preset.family];\n\n    // The ramp is looked up by name, so its type has to be widened to index the primitives and then\n    // narrowed again for `definePreset`. `ColorScale` is the shape every primitive color in a preset has -\n    // the 50..950 steps - and `primaryColor` is only ever one of those names, guaranteed by the catalog.\n    const primitives = base.primitive as unknown as Record<string, Record<string, string>>;\n    const ramp = primitives[preset.primaryColor];\n    const built = definePreset(base, { semantic: { primary: ramp } }) as PrimeReactPreset;\n\n    presetCache.set(themeName, built);\n    return built;\n}\n"],"names":["basePresets","PrimeReactThemeFamily","Aura","Lara","Nora","Material","presetCache","Map","primeReactThemePreset","themeName","cached","get","undefined","preset","themePresets","find","candidate","name","base","family","primitives","primitive","ramp","primaryColor","built","definePreset","semantic","primary","set"],"mappings":";;;;;;;;;;AAAA;AACA;AAmBA;;;;;;;AAOC,IACD,MAAMA,WAAAA,GAA+D;IACjE,CAACC,2CAAAA,CAAsBC,IAAI,GAAGA,IAAAA;IAC9B,CAACD,2CAAAA,CAAsBE,IAAI,GAAGA,IAAAA;IAC9B,CAACF,2CAAAA,CAAsBG,IAAI,GAAGA,IAAAA;IAC9B,CAACH,2CAAAA,CAAsBI,QAAQ,GAAGA;AACtC,CAAA;AAEA;;;;;;;IAQA,MAAMC,cAAc,IAAIC,GAAAA,EAAAA;AAExB;;;;;;;;;;;;;;;;;;IAmBO,SAASC,qBAAAA,CAAsBC,SAAiB,EAAA;IACnD,MAAMC,MAAAA,GAASJ,WAAAA,CAAYK,GAAG,CAACF,SAAAA,CAAAA;IAC/B,IAAIC,MAAAA,KAAWE,WAAW,OAAOF,MAAAA;IAEjC,MAAMG,MAAAA,GAASC,0BAAaC,IAAI,CAAC,CAACC,SAAAA,GAAcA,SAAAA,CAAUC,IAAI,KAAKR,SAAAA,CAAAA;IACnE,IAAII,MAAAA,KAAWD,WAAW,OAAOA,SAAAA;AAEjC,IAAA,MAAMM,IAAAA,GAAOlB,WAAW,CAACa,MAAAA,CAAOM,MAAM,CAAC;;;;IAKvC,MAAMC,UAAAA,GAAaF,KAAKG,SAAS;AACjC,IAAA,MAAMC,IAAAA,GAAOF,UAAU,CAACP,MAAAA,CAAOU,YAAY,CAAC;IAC5C,MAAMC,KAAAA,GAAQC,oBAAaP,IAAAA,EAAM;QAAEQ,QAAAA,EAAU;YAAEC,OAAAA,EAASL;AAAK;AAAE,KAAA,CAAA;IAE/DhB,WAAAA,CAAYsB,GAAG,CAACnB,SAAAA,EAAWe,KAAAA,CAAAA;IAC3B,OAAOA,KAAAA;AACX;;;;"}

package/dist/cjs/theme/primeReactThemes.js

@@ -7,15 +7,16 @@ var themePresets = require('./themePresets.js');
 /**
  * The packages a PrimeReact theme declares itself compatible with.
  *
- * `PrimeReact` and `Tailwind` are obvious - the stylesheet skins PrimeReact's components, and this
- * package's own wrappers lay themselves out with Tailwind utilities.
+ * `PrimeReact` and `Tailwind` are obvious - the preset skins PrimeReact's components, and this package's
+ * own wrappers lay themselves out with Tailwind utilities.
  *
  * `core` is the interesting one, and it is listed deliberately rather than by reflex. A theme reaches a
- * screen in two layers: a stylesheet that only ever matches PrimeReact's own `.p-*` elements, and a set
- * of semantic Scene tokens that `SceneThemeProvider` writes onto the wrapping element. The second layer
- * applies to *everything* underneath it, `core`'s unstyled primitives included - they inherit the
- * theme's type color and can read any token they choose to. So the claim being made is precise: these
- * themes genuinely reach `core`'s components, through tokens rather than through the component skin.
+ * screen in two layers: the `--p-*` custom properties `@primeuix/styled` emits for the active preset,
+ * which only PrimeReact's own components read, and a set of semantic Scene tokens that
+ * `SceneThemeProvider` writes onto the wrapping element. The second layer applies to *everything*
+ * underneath it, `core`'s unstyled primitives included - they inherit the theme's type color and can read
+ * any token they choose to. So the claim being made is precise: these themes genuinely reach `core`'s
+ * components, through tokens rather than through the component skin.
  *
  * This has to be said explicitly because `ThemeCompatibility` has no implicit exemption for `core`. A
  * theme that leaves it out is reported incompatible for every profile that lists `core`, which for a
@@ -26,23 +27,39 @@ var themePresets = require('./themePresets.js');
     'core'
 ];
 /**
- * Every free PrimeReact 10 theme this package ships, as Scene {@link Theme}s.
+ * The license every theme in this catalog is published under.
  *
- * None of these themes are ours. They are PrimeTek's, shipped under the MIT license that covers the
- * whole `primereact` package (verified in `node_modules/primereact/LICENSE.md`: "The MIT License (MIT),
- * Copyright (c) 2016-2025 PrimeTek"). Redistributing them without saying so would be dishonest, which is
- * what `Theme`'s `author`, `authorUrl` and `license` fields exist to prevent - and why the credit is
- * applied here, once, to every preset, rather than written out per theme where it could be forgotten.
+ * This is **not** MIT, and the difference matters enough to be a named constant rather than a string
+ * repeated twenty-four times. PrimeReact 10 - presets included - was MIT. PrimeReact 11 relicensed the
+ * entire stack (`primereact`, `@primereact/core`, `@primereact/headless`, `primeicons`,
+ * `@primeuix/themes`, `@primeuix/styled`) under the commercial PrimeUI license, which requires a license
+ * key: without one, `PrimeReactProvider` warns on the console and injects an "Invalid PrimeUI License"
+ * banner, in development and production alike.
  *
- * Several themes are PrimeTek's interpretation of someone else's design language - Bootstrap, Material
- * Design, Fluent, Tailwind UI. The compiled CSS is still PrimeTek's own work, so PrimeTek is still the
- * author; the lineage is recorded in each theme's description instead of by misattributing the file.
+ * `Theme`'s `license` field exists so a theme picker, an audit, or a person reading the catalog can see
+ * what they are actually taking on. Reporting these as MIT because the *previous* major was MIT is the
+ * exact mistake the field is there to prevent.
+ *
+ * @see https://primeui.dev/licenses/community for the free community tier and its eligibility limits.
+ * @see https://primeui.dev/licenses/commercial for the paid tier.
+ */ const primeReactThemeLicense = 'PrimeUI Commercial';
+/**
+ * Every theme this package ships, as Scene {@link Theme}s.
+ *
+ * None of these themes are ours. They are PrimeTek's `@primeuix/themes` presets - Aura, Lara, Nora and
+ * Material - with one of the preset's own primitive color ramps bound to its primary scale. Choosing
+ * which accent to bind is the only design decision Scene makes here, and it is not enough to claim
+ * authorship over: the surface ramps, the radii, the focus rings, the component styling and the design
+ * language are all PrimeTek's work.
+ *
+ * That is what `Theme`'s `author`, `authorUrl` and `license` fields exist to record, and why the credit
+ * is applied here, once, to every preset, rather than written out per theme where it could be forgotten.
  */ const primeReactThemes = themePresets.themePresets.map((preset)=>({
         ...preset,
         compatibleWith: primeReactThemeCompatibility,
         author: 'PrimeTek',
         authorUrl: 'https://primereact.org',
-        license: 'MIT'
+        license: primeReactThemeLicense
     }));
 /**
  * The names of every theme this package ships, in catalog order - what the manifest declares and what a
@@ -51,7 +68,7 @@ var themePresets = require('./themePresets.js');
 /**
  * Finds one of this package's themes by name.
  *
- * @param name The theme name, which is also its folder under `primereact/resources/themes`.
+ * @param name The theme name.
  * @returns The theme, or `undefined` when this package does not ship one by that name.
  */ function primeReactTheme(name) {
     return primeReactThemes.find((theme)=>theme.name === name);
@@ -59,6 +76,7 @@ var themePresets = require('./themePresets.js');
 
 exports.primeReactTheme = primeReactTheme;
 exports.primeReactThemeCompatibility = primeReactThemeCompatibility;
+exports.primeReactThemeLicense = primeReactThemeLicense;
 exports.primeReactThemeNames = primeReactThemeNames;
 exports.primeReactThemes = primeReactThemes;
 //# sourceMappingURL=primeReactThemes.js.map

package/dist/cjs/theme/primeReactThemes.js.map

@@ -1 +1 @@
-{"version":3,"file":"primeReactThemes.js","sources":["../../../theme/primeReactThemes.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Theme } from '@cratis/scene.model';\nimport { themePresets } from './themePresets';\n\n/**\n * The packages a PrimeReact theme declares itself compatible with.\n *\n * `PrimeReact` and `Tailwind` are obvious - the stylesheet skins PrimeReact's components, and this\n * package's own wrappers lay themselves out with Tailwind utilities.\n *\n * `core` is the interesting one, and it is listed deliberately rather than by reflex. A theme reaches a\n * screen in two layers: a stylesheet that only ever matches PrimeReact's own `.p-*` elements, and a set\n * of semantic Scene tokens that `SceneThemeProvider` writes onto the wrapping element. The second layer\n * applies to *everything* underneath it, `core`'s unstyled primitives included - they inherit the\n * theme's type color and can read any token they choose to. So the claim being made is precise: these\n * themes genuinely reach `core`'s components, through tokens rather than through the component skin.\n *\n * This has to be said explicitly because `ThemeCompatibility` has no implicit exemption for `core`. A\n * theme that leaves it out is reported incompatible for every profile that lists `core`, which for a\n * theme that really does apply would be a false alarm on nearly every profile there is.\n */\nexport const primeReactThemeCompatibility: string[] = ['PrimeReact', 'Tailwind', 'core'];\n\n/**\n * Every free PrimeReact 10 theme this package ships, as Scene {@link Theme}s.\n *\n * None of these themes are ours. They are PrimeTek's, shipped under the MIT license that covers the\n * whole `primereact` package (verified in `node_modules/primereact/LICENSE.md`: \"The MIT License (MIT),\n * Copyright (c) 2016-2025 PrimeTek\"). Redistributing them without saying so would be dishonest, which is\n * what `Theme`'s `author`, `authorUrl` and `license` fields exist to prevent - and why the credit is\n * applied here, once, to every preset, rather than written out per theme where it could be forgotten.\n *\n * Several themes are PrimeTek's interpretation of someone else's design language - Bootstrap, Material\n * Design, Fluent, Tailwind UI. The compiled CSS is still PrimeTek's own work, so PrimeTek is still the\n * author; the lineage is recorded in each theme's description instead of by misattributing the file.\n */\nexport const primeReactThemes: Theme[] = themePresets.map((preset) => ({\n    ...preset,\n    compatibleWith: primeReactThemeCompatibility,\n    author: 'PrimeTek',\n    authorUrl: 'https://primereact.org',\n    license: 'MIT',\n}));\n\n/**\n * The names of every theme this package ships, in catalog order - what the manifest declares and what a\n * theme picker lists.\n */\nexport const primeReactThemeNames: string[] = primeReactThemes.map((theme) => theme.name);\n\n/**\n * Finds one of this package's themes by name.\n *\n * @param name The theme name, which is also its folder under `primereact/resources/themes`.\n * @returns The theme, or `undefined` when this package does not ship one by that name.\n */\nexport function primeReactTheme(name: string): Theme | undefined {\n    return primeReactThemes.find((theme) => theme.name === name);\n}\n"],"names":["primeReactThemeCompatibility","primeReactThemes","themePresets","map","preset","compatibleWith","author","authorUrl","license","primeReactThemeNames","theme","name","primeReactTheme","find"],"mappings":";;;;AAAA;AACA;AAKA;;;;;;;;;;;;;;;;UAiBaA,4BAAAA,GAAyC;AAAC,IAAA,YAAA;AAAc,IAAA,UAAA;AAAY,IAAA;;AAEjF;;;;;;;;;;;;UAaaC,gBAAAA,GAA4BC,yBAAAA,CAAaC,GAAG,CAAC,CAACC,UAAY;AACnE,QAAA,GAAGA,MAAM;QACTC,cAAAA,EAAgBL,4BAAAA;QAChBM,MAAAA,EAAQ,UAAA;QACRC,SAAAA,EAAW,wBAAA;QACXC,OAAAA,EAAS;AACb,KAAA,CAAA;AAEA;;;IAIO,MAAMC,oBAAAA,GAAiCR,gBAAAA,CAAiBE,GAAG,CAAC,CAACO,KAAAA,GAAUA,KAAAA,CAAMC,IAAI;AAExF;;;;;IAMO,SAASC,eAAAA,CAAgBD,IAAY,EAAA;AACxC,IAAA,OAAOV,iBAAiBY,IAAI,CAAC,CAACH,KAAAA,GAAUA,KAAAA,CAAMC,IAAI,KAAKA,IAAAA,CAAAA;AAC3D;;;;;;;"}
+{"version":3,"file":"primeReactThemes.js","sources":["../../../theme/primeReactThemes.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Theme } from '@cratis/scene.model';\nimport { themePresets } from './themePresets';\n\n/**\n * The packages a PrimeReact theme declares itself compatible with.\n *\n * `PrimeReact` and `Tailwind` are obvious - the preset skins PrimeReact's components, and this package's\n * own wrappers lay themselves out with Tailwind utilities.\n *\n * `core` is the interesting one, and it is listed deliberately rather than by reflex. A theme reaches a\n * screen in two layers: the `--p-*` custom properties `@primeuix/styled` emits for the active preset,\n * which only PrimeReact's own components read, and a set of semantic Scene tokens that\n * `SceneThemeProvider` writes onto the wrapping element. The second layer applies to *everything*\n * underneath it, `core`'s unstyled primitives included - they inherit the theme's type color and can read\n * any token they choose to. So the claim being made is precise: these themes genuinely reach `core`'s\n * components, through tokens rather than through the component skin.\n *\n * This has to be said explicitly because `ThemeCompatibility` has no implicit exemption for `core`. A\n * theme that leaves it out is reported incompatible for every profile that lists `core`, which for a\n * theme that really does apply would be a false alarm on nearly every profile there is.\n */\nexport const primeReactThemeCompatibility: string[] = ['PrimeReact', 'Tailwind', 'core'];\n\n/**\n * The license every theme in this catalog is published under.\n *\n * This is **not** MIT, and the difference matters enough to be a named constant rather than a string\n * repeated twenty-four times. PrimeReact 10 - presets included - was MIT. PrimeReact 11 relicensed the\n * entire stack (`primereact`, `@primereact/core`, `@primereact/headless`, `primeicons`,\n * `@primeuix/themes`, `@primeuix/styled`) under the commercial PrimeUI license, which requires a license\n * key: without one, `PrimeReactProvider` warns on the console and injects an \"Invalid PrimeUI License\"\n * banner, in development and production alike.\n *\n * `Theme`'s `license` field exists so a theme picker, an audit, or a person reading the catalog can see\n * what they are actually taking on. Reporting these as MIT because the *previous* major was MIT is the\n * exact mistake the field is there to prevent.\n *\n * @see https://primeui.dev/licenses/community for the free community tier and its eligibility limits.\n * @see https://primeui.dev/licenses/commercial for the paid tier.\n */\nexport const primeReactThemeLicense = 'PrimeUI Commercial';\n\n/**\n * Every theme this package ships, as Scene {@link Theme}s.\n *\n * None of these themes are ours. They are PrimeTek's `@primeuix/themes` presets - Aura, Lara, Nora and\n * Material - with one of the preset's own primitive color ramps bound to its primary scale. Choosing\n * which accent to bind is the only design decision Scene makes here, and it is not enough to claim\n * authorship over: the surface ramps, the radii, the focus rings, the component styling and the design\n * language are all PrimeTek's work.\n *\n * That is what `Theme`'s `author`, `authorUrl` and `license` fields exist to record, and why the credit\n * is applied here, once, to every preset, rather than written out per theme where it could be forgotten.\n */\nexport const primeReactThemes: Theme[] = themePresets.map((preset) => ({\n    ...preset,\n    compatibleWith: primeReactThemeCompatibility,\n    author: 'PrimeTek',\n    authorUrl: 'https://primereact.org',\n    license: primeReactThemeLicense,\n}));\n\n/**\n * The names of every theme this package ships, in catalog order - what the manifest declares and what a\n * theme picker lists.\n */\nexport const primeReactThemeNames: string[] = primeReactThemes.map((theme) => theme.name);\n\n/**\n * Finds one of this package's themes by name.\n *\n * @param name The theme name.\n * @returns The theme, or `undefined` when this package does not ship one by that name.\n */\nexport function primeReactTheme(name: string): Theme | undefined {\n    return primeReactThemes.find((theme) => theme.name === name);\n}\n"],"names":["primeReactThemeCompatibility","primeReactThemeLicense","primeReactThemes","themePresets","map","preset","compatibleWith","author","authorUrl","license","primeReactThemeNames","theme","name","primeReactTheme","find"],"mappings":";;;;AAAA;AACA;AAKA;;;;;;;;;;;;;;;;;UAkBaA,4BAAAA,GAAyC;AAAC,IAAA,YAAA;AAAc,IAAA,UAAA;AAAY,IAAA;;AAEjF;;;;;;;;;;;;;;;;IAiBO,MAAMC,sBAAAA,GAAyB;AAEtC;;;;;;;;;;;UAYaC,gBAAAA,GAA4BC,yBAAAA,CAAaC,GAAG,CAAC,CAACC,UAAY;AACnE,QAAA,GAAGA,MAAM;QACTC,cAAAA,EAAgBN,4BAAAA;QAChBO,MAAAA,EAAQ,UAAA;QACRC,SAAAA,EAAW,wBAAA;QACXC,OAAAA,EAASR;AACb,KAAA,CAAA;AAEA;;;IAIO,MAAMS,oBAAAA,GAAiCR,gBAAAA,CAAiBE,GAAG,CAAC,CAACO,KAAAA,GAAUA,KAAAA,CAAMC,IAAI;AAExF;;;;;IAMO,SAASC,eAAAA,CAAgBD,IAAY,EAAA;AACxC,IAAA,OAAOV,iBAAiBY,IAAI,CAAC,CAACH,KAAAA,GAAUA,KAAAA,CAAMC,IAAI,KAAKA,IAAAA,CAAAA;AAC3D;;;;;;;;"}