@poodle64/ui 2026.10.15 → 2026.10.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/dist/components/ui/app-shell/app-shell.svelte +6 -5
  2. package/package.json +1 -1
  3. package/registry/component-map.json +1 -1
  4. package/registry/component-map.md +1 -1
package/dist/components/ui/app-shell/app-shell.svelte CHANGED
@@ -825,11 +825,12 @@
825
825
  -->
826
826
  <!--
827
827
  `measure` caps and centres this box, through `.ds-shell-measure`
828
- in styles.css rather than a utility here — an arbitrary
829
- `max-w-[var(…)]` only exists if the consumer's Tailwind build
830
- scanned the file spelling it, and a cap that silently does not
831
- compile is the failure mode this package gates against everywhere
832
- else.
828
+ in styles.css rather than a utility here — an arbitrary max-width
829
+ utility only exists if the consumer's Tailwind build scanned the
830
+ file spelling it, and a cap that silently does not compile is the
831
+ failure mode this package gates against everywhere else. (Never
832
+ write the utility's class name in a comment: Tailwind scans
833
+ comments too, and compiles the placeholder it finds there.)
833
834
 
834
835
  At `full` the class and the attribute are both ABSENT, not set to
835
836
  a no-op value. That is what makes the prop additive: a consumer
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@poodle64/ui",
3
- "version": "2026.10.15",
3
+ "version": "2026.10.16",
4
4
  "description": "Household shared component layer: shadcn-svelte primitives (bits-ui) plus the composed page chrome every app builds its routes from, restyled by each app's @poodle64/design-tokens alias layer. One fix reaches every app.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/registry/component-map.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "meta": {
3
3
  "package": "@poodle64/ui",
4
- "version": "2026.10.15",
4
+ "version": "2026.10.16",
5
5
  "generatedBy": "scripts/generate-registry.mjs",
6
6
  "source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
7
7
  "componentCount": 69,
package/registry/component-map.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # @poodle64/ui — situation → component map
2
2
 
3
3
  <!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
4
- Generated from `@poodle64/ui@2026.10.15`. 69 components, 19 situations.
4
+ Generated from `@poodle64/ui@2026.10.16`. 69 components, 19 situations.
5
5
 
6
6
  **Read this before writing a `<div>`.** Find the SITUATION you are in below, then compose the component named for it — do not hand-build it from raw `Card` or utility classes. Import is `import { Name } from '<import path>'`. Props marked `?` are optional. This map is the retrieval step the [`frontend-design` skill] makes mandatory; the [CHI 2026 study] measured composing-from-a-registry at 95% design-system compliance against 71% for writing the CSS from a prose style guide.
7
7