@pieai/swimmer-ui-kit 1.11.1 → 1.11.2

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 (3) hide show
  1. package/CHANGELOG.md +28 -29
  2. package/dist/index.js +738 -741
  3. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -5,37 +5,36 @@ Format: [Keep a Changelog](https://keepachangelog.com); versioning: semver.
5
5
 
6
6
  ## Unreleased
7
7
 
8
+ ## 1.11.2
9
+
10
+ ### Fixed
11
+
12
+ - **The budget warnings were dead in every published build.** Both budget
13
+ fallbacks — the animation engine's and Melt/dissolve's — were gated on
14
+ `import.meta.env.DEV`. That flag resolves when *this package* is built, not
15
+ when the app importing it is, so it was baked to `false` in the artifact and
16
+ the guard minified to `if (this.budgetWarningEmitted || !0) return;` — an
17
+ unconditional early return. The kit degraded to static rendering silently,
18
+ which is precisely the behaviour those warnings were added to make visible.
19
+ They are no longer gated on build mode: a group that stops animating says so
20
+ once, in whatever build the consumer is running. `isDev()` is gone entirely,
21
+ along with the two authoring warnings it silenced; a library cannot detect
22
+ its consumer's build mode, and trying to is what caused this.
23
+
8
24
  ### Added
9
25
 
10
- - **Morph shape evolution and content cross-blur.** `LiquidGroup.Item` now
11
- accepts `morph={{ shape, speed, bounce, contentBlur }}`. The adopted centre
12
- size corner timeline makes the liquid change form like jelly, while the
13
- default `contentBlur: 7` is written to the content wrapper only and clears as
14
- the motion settles. The brand-kit token default deliberately enables shape;
15
- pass `shape: false` for a calm opt-out.
16
- - **Surface-glued Bend.** `effect="bend"` follows an externally moved child,
17
- bows its long edges and deforms its rounded caps without a lagging body or
18
- tail. It publishes `--lg-bend-x`, `--lg-bend-y`, `--lg-bend-xn`, and
19
- `--lg-bend-yn` on the item for content tilt/rotation.
20
- - **Knob stories and budget evidence.** Storybook now exposes conservative,
21
- default, and bold points for Morph and Bend, plus contentBlur off/default/bold
22
- comparisons and a combined filter-area readout.
23
-
24
- ### Performance
25
-
26
- - Morph content-blur and Bend deformation slack are part of the existing
27
- 480,000 CSS-pixel filter-area ceiling. The shared requestAnimationFrame clock
28
- remains event-driven and sleeps completely after stillness; an over-budget
29
- group snaps to static filtered rendering with a development warning.
30
- - **Image Melt and contact dissolve for `LiquidGroup.Item`.** The first two
31
- `effect="melt"` items now render the donor-shaped measured image pair with
32
- crisp-face seam masks, two-palette colour mixing, and a visible marbling
33
- pass. `dissolve` is an image-only contact modifier with liquid displacement
34
- and release hysteresis; DOM text stays in the crisp content layer, and the
35
- modifier is ignored with a development warning under `effect="move"`.
36
- Numeric knobs are token-backed, share the 480,000 px² filter-area and
37
- process-wide concurrency budgets, degrade visibly with a one-time warning
38
- when over budget, and sleep their requestAnimationFrame clock at rest.
26
+ - **`scripts/check-warnings-survive-build.mjs`, wired into `build`.** The defect
27
+ above is invisible in the source and invisible to the test suite; it exists
28
+ only in the bundled output. So the check reads the bundled output, and fails
29
+ if a promised warning is missing or its guard has been folded to a constant.
30
+ Verified by reintroducing the bug and watching it fail.
31
+
32
+ ### Note
33
+
34
+ - The previous `Unreleased` section listed Morph shape, Bend, Melt and the knob
35
+ stories as unshipped. They shipped in 1.11.0. The entries were left behind by
36
+ the branch merges and have been removed rather than re-dated, since 1.11.0
37
+ already describes the same work.
39
38
 
40
39
  ## 1.11.1
41
40