@the-portland-company/shell 0.28.2 → 0.30.0
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.
- package/CHANGELOG.md +29 -0
- package/dist/app-chrome.cjs.map +1 -1
- package/dist/app-chrome.js +1 -1
- package/dist/{chunk-I3DWBWY6.js → chunk-QL5BWYN5.js} +4 -4
- package/dist/chunk-QL5BWYN5.js.map +1 -0
- package/dist/native.cjs +1 -0
- package/dist/native.cjs.map +1 -1
- package/dist/native.d.cts +28 -1
- package/dist/native.d.ts +28 -1
- package/dist/native.js +1 -1
- package/dist/runtime-tokens.cjs +19 -0
- package/dist/runtime-tokens.cjs.map +1 -0
- package/dist/runtime-tokens.d.cts +4 -0
- package/dist/runtime-tokens.d.ts +4 -0
- package/dist/runtime-tokens.js +16 -0
- package/dist/runtime-tokens.js.map +1 -0
- package/package.json +6 -1
- package/dist/chunk-I3DWBWY6.js.map +0 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,32 @@
|
|
|
1
|
+
## 0.30.0 — 2026-07-23
|
|
2
|
+
|
|
3
|
+
### Added — `TopBarPopover` is public (enables the VRM widget port)
|
|
4
|
+
|
|
5
|
+
The shared top-bar popover — 32px circular trigger, standard tooltip, count
|
|
6
|
+
badge, right-aligned panel with the pointer arrow — was private, so an app with
|
|
7
|
+
a richer panel than the stock actions (VRM: fuel breakdown, import progress,
|
|
8
|
+
system alerts, reply feed) had no way to render it inside the shared chrome and
|
|
9
|
+
hand-rolled its own trigger instead. That is the last structural reason VRM's
|
|
10
|
+
top bar differs from forms/polls/surveys/contacts.
|
|
11
|
+
|
|
12
|
+
Exporting it lets those panels move into the shared cluster **one at a time**,
|
|
13
|
+
each keeping its behavior — rather than a wholesale swap to the generic actions,
|
|
14
|
+
which would drop capability VRM already ships (UI-Platform explicitly forbids
|
|
15
|
+
migrating an app to a rendering that loses an element it has).
|
|
16
|
+
|
|
17
|
+
## 0.29.0 — 2026-07-23
|
|
18
|
+
|
|
19
|
+
### Added — `./runtime-tokens` (`ensureRuntimeBrandTokens`)
|
|
20
|
+
|
|
21
|
+
A static `<link>` to `/api/tokens?format=css` in `<head>` is not sufficient on
|
|
22
|
+
its own: an app's own bundled `chrome.css` can be injected AFTER it and win the
|
|
23
|
+
cascade. VRM linked the runtime sheet and still resolved `--color-accent` from
|
|
24
|
+
the build-time snapshot, so a Brand edit reached four apps and not the fifth.
|
|
25
|
+
|
|
26
|
+
`ensureRuntimeBrandTokens()` appends (or moves) the tokens link to the END of
|
|
27
|
+
`<head>` at startup, making the live Brand values last in the cascade for every
|
|
28
|
+
app. Idempotent, and the response's ETag + `max-age=60` means no extra fetch.
|
|
29
|
+
|
|
1
30
|
## 0.28.2 — 2026-07-23
|
|
2
31
|
|
|
3
32
|
### Fixed — the Chakra theme hardcoded the body font
|