@roxyapi/ui 1.1.1 → 1.1.3
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/AGENTS.md +5 -5
- package/README.md +3 -3
- package/THEMING.md +3 -3
- package/components-catalog.json +258 -158
- package/dist/cdn/components/almanac-day.js +3 -205
- package/dist/cdn/components/angel-number-card.js +3 -205
- package/dist/cdn/components/angel-number-lookup.js +3 -205
- package/dist/cdn/components/arudha-padas.js +3 -205
- package/dist/cdn/components/ashtakavarga-grid.js +3 -205
- package/dist/cdn/components/aspects-table.js +3 -205
- package/dist/cdn/components/astrocartography-map.js +3 -205
- package/dist/cdn/components/bazi-chart.js +3 -205
- package/dist/cdn/components/bhav-chalit-table.js +2 -204
- package/dist/cdn/components/bhava-bala-table.js +3 -205
- package/dist/cdn/components/biorhythm-chart.js +3 -205
- package/dist/cdn/components/bodygraph.js +7 -209
- package/dist/cdn/components/chara-karakas.js +3 -205
- package/dist/cdn/components/choghadiya-grid.js +3 -205
- package/dist/cdn/components/compatibility-card.js +2 -204
- package/dist/cdn/components/compound-number.js +3 -205
- package/dist/cdn/components/crystal-card.js +3 -205
- package/dist/cdn/components/crystal-grid.js +3 -205
- package/dist/cdn/components/dasha-timeline.js +3 -205
- package/dist/cdn/components/data.js +3 -205
- package/dist/cdn/components/divisional-chart.js +13 -215
- package/dist/cdn/components/dosha-card.js +3 -205
- package/dist/cdn/components/dosha-constitution.js +3 -205
- package/dist/cdn/components/dream-card.js +3 -205
- package/dist/cdn/components/dream-search.js +3 -205
- package/dist/cdn/components/endpoint-form.js +3 -205
- package/dist/cdn/components/ephemeris-table.js +2 -204
- package/dist/cdn/components/fixed-stars.js +2 -204
- package/dist/cdn/components/flying-star-chart.js +2 -204
- package/dist/cdn/components/forecast-digest.js +3 -205
- package/dist/cdn/components/forecast-timeline.js +3 -205
- package/dist/cdn/components/gematria.js +3 -205
- package/dist/cdn/components/gochara-table.js +3 -205
- package/dist/cdn/components/guna-milan.js +3 -205
- package/dist/cdn/components/hd-connection.js +5 -207
- package/dist/cdn/components/hd-penta.js +5 -207
- package/dist/cdn/components/hd-type-card.js +3 -205
- package/dist/cdn/components/hd-variables.js +3 -205
- package/dist/cdn/components/heliacal-table.js +3 -205
- package/dist/cdn/components/hexagram.js +3 -205
- package/dist/cdn/components/hora-table.js +3 -205
- package/dist/cdn/components/horoscope-card.js +3 -205
- package/dist/cdn/components/kp-chart.js +3 -205
- package/dist/cdn/components/kp-finance-card.js +3 -205
- package/dist/cdn/components/kp-planets-table.js +3 -205
- package/dist/cdn/components/kp-ruling-planets.js +3 -205
- package/dist/cdn/components/kua-card.js +3 -205
- package/dist/cdn/components/local-space-compass.js +8 -210
- package/dist/cdn/components/location-search.js +3 -205
- package/dist/cdn/components/luck-pillars.js +3 -205
- package/dist/cdn/components/mayan-day-sign.js +3 -205
- package/dist/cdn/components/moon-phase.js +3 -205
- package/dist/cdn/components/nakshatra-card.js +3 -205
- package/dist/cdn/components/natal-chart.js +6 -208
- package/dist/cdn/components/numerology-card.js +3 -205
- package/dist/cdn/components/panchang-table.js +3 -205
- package/dist/cdn/components/positions-table.js +3 -205
- package/dist/cdn/components/profection-card.js +3 -205
- package/dist/cdn/components/reference-card.js +3 -205
- package/dist/cdn/components/relocation-wheel.js +6 -208
- package/dist/cdn/components/shadbala-table.js +3 -205
- package/dist/cdn/components/synastry-chart.js +7 -209
- package/dist/cdn/components/tarot-card.js +3 -205
- package/dist/cdn/components/tarot-catalog.js +3 -205
- package/dist/cdn/components/tarot-spread.js +3 -205
- package/dist/cdn/components/transit-wheel.js +8 -210
- package/dist/cdn/components/transits-table.js +3 -205
- package/dist/cdn/components/upagraha-table.js +2 -204
- package/dist/cdn/components/vastu-mandala.js +4 -206
- package/dist/cdn/components/vedic-aspects.js +2 -204
- package/dist/cdn/components/vedic-daily.js +3 -205
- package/dist/cdn/components/vedic-kundli.js +10 -212
- package/dist/cdn/components/vedic-planets-table.js +3 -205
- package/dist/cdn/components/western-planets-table.js +2 -204
- package/dist/cdn/components/yoga-list.js +3 -205
- package/dist/cdn/components/zodiac-card.js +2 -204
- package/dist/cdn/locales/de.js +1 -1
- package/dist/cdn/roxy-ui.js +49 -251
- package/dist/components/almanac-day.js +1 -203
- package/dist/components/angel-number-card.js +1 -203
- package/dist/components/angel-number-lookup.js +1 -203
- package/dist/components/arudha-padas.js +1 -203
- package/dist/components/ashtakavarga-grid.js +1 -203
- package/dist/components/aspects-table.js +1 -203
- package/dist/components/astrocartography-map.js +6 -208
- package/dist/components/bazi-chart.js +1 -203
- package/dist/components/bhav-chalit-table.js +1 -203
- package/dist/components/bhava-bala-table.js +1 -203
- package/dist/components/biorhythm-chart.js +1 -203
- package/dist/components/bodygraph.js +3 -205
- package/dist/components/chara-karakas.js +1 -203
- package/dist/components/choghadiya-grid.js +1 -203
- package/dist/components/compatibility-card.js +1 -203
- package/dist/components/compound-number.js +1 -203
- package/dist/components/crystal-card.js +1 -203
- package/dist/components/crystal-grid.js +1 -203
- package/dist/components/dasha-timeline.js +1 -203
- package/dist/components/data.js +1 -203
- package/dist/components/divisional-chart.js +45 -247
- package/dist/components/dosha-card.js +1 -203
- package/dist/components/dosha-constitution.js +1 -203
- package/dist/components/dream-card.js +1 -203
- package/dist/components/dream-search.js +1 -203
- package/dist/components/endpoint-form.js +1 -203
- package/dist/components/ephemeris-table.js +1 -203
- package/dist/components/fixed-stars.js +1 -203
- package/dist/components/flying-star-chart.js +1 -203
- package/dist/components/forecast-digest.js +1 -203
- package/dist/components/forecast-timeline.js +1 -203
- package/dist/components/gematria.js +1 -203
- package/dist/components/gochara-table.js +1 -203
- package/dist/components/guna-milan.js +1 -203
- package/dist/components/hd-connection.js +3 -205
- package/dist/components/hd-penta.js +5 -207
- package/dist/components/hd-type-card.js +1 -203
- package/dist/components/hd-variables.js +1 -203
- package/dist/components/heliacal-table.js +1 -203
- package/dist/components/hexagram.d.ts +1 -1
- package/dist/components/hexagram.js +1 -203
- package/dist/components/hora-table.js +1 -203
- package/dist/components/horoscope-card.js +1 -203
- package/dist/components/kp-chart.js +1 -203
- package/dist/components/kp-finance-card.js +1 -203
- package/dist/components/kp-planets-table.js +1 -203
- package/dist/components/kp-ruling-planets.js +1 -203
- package/dist/components/kua-card.js +1 -203
- package/dist/components/local-space-compass.js +4 -206
- package/dist/components/location-search.js +1 -203
- package/dist/components/luck-pillars.js +1 -203
- package/dist/components/mayan-day-sign.js +1 -203
- package/dist/components/moon-phase.js +1 -203
- package/dist/components/nakshatra-card.js +1 -203
- package/dist/components/natal-chart.d.ts +1 -1
- package/dist/components/natal-chart.js +5 -207
- package/dist/components/numerology-card.js +1 -203
- package/dist/components/panchang-table.js +1 -203
- package/dist/components/positions-table.js +1 -203
- package/dist/components/profection-card.js +1 -203
- package/dist/components/reference-card.js +1 -203
- package/dist/components/relocation-wheel.js +3 -205
- package/dist/components/shadbala-table.js +1 -203
- package/dist/components/synastry-chart.js +6 -208
- package/dist/components/tarot-card.js +1 -203
- package/dist/components/tarot-catalog.js +1 -203
- package/dist/components/tarot-spread.js +1 -203
- package/dist/components/transit-wheel.js +8 -210
- package/dist/components/transits-table.js +1 -203
- package/dist/components/upagraha-table.js +1 -203
- package/dist/components/vastu-mandala.js +6 -208
- package/dist/components/vedic-aspects.js +1 -203
- package/dist/components/vedic-daily.js +1 -203
- package/dist/components/vedic-kundli.js +15 -217
- package/dist/components/vedic-planets-table.js +1 -203
- package/dist/components/western-planets-table.js +1 -203
- package/dist/components/yoga-list.js +1 -203
- package/dist/components/zodiac-card.js +1 -203
- package/dist/forms.json +1 -1
- package/dist/index.cjs +49 -251
- package/dist/index.js +50 -252
- package/dist/locales/de.js +1 -1
- package/dist/schemas/post--astrology-lilith.json +1 -1
- package/dist/schemas/post--astrology-progressions.json +1 -1
- package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
- package/dist/schemas/post--numerology-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-daily.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit.json +1 -1
- package/dist/styles/palettes.d.ts +4 -0
- package/dist/styles/themes/celeste.css +1 -115
- package/dist/styles/themes/eucalyptus.css +1 -121
- package/dist/styles/themes/kiln.css +1 -121
- package/dist/styles/themes/moonlit.css +1 -121
- package/dist/styles/themes/practitioner.css +1 -170
- package/dist/styles/tokens-css.d.ts +1 -1
- package/dist/styles/tokens.css +1 -202
- package/dist/types/types.gen.d.ts +48 -36
- package/dist/utils/string.d.ts +2 -0
- package/dist/version.d.ts +1 -1
- package/package.json +1 -1
package/AGENTS.md
CHANGED
|
@@ -261,7 +261,7 @@ import { RoxyVedicKundli, RoxyLocationSearch } from '@roxyapi/ui-vue';
|
|
|
261
261
|
</template>
|
|
262
262
|
```
|
|
263
263
|
|
|
264
|
-
In Nuxt, render them in any page or component, server rendered or not: the markup renders on the server and the element hydrates in the browser, with no `<ClientOnly>`
|
|
264
|
+
In Nuxt, render them in any page or component, server rendered or not: the markup renders on the server and the element hydrates in the browser, with no `<ClientOnly>` boundary.
|
|
265
265
|
|
|
266
266
|
### 7. Local response interface drift
|
|
267
267
|
|
|
@@ -315,7 +315,7 @@ const data = natal as unknown as NatalChartResponse;
|
|
|
315
315
|
|
|
316
316
|
### 11. The components load from a CDN. Self-host if your CSP forbids that.
|
|
317
317
|
|
|
318
|
-
On first mount the components fetch their rendering bundle from the CDN, pinned to the exact `@roxyapi/ui` release the
|
|
318
|
+
On first mount the components fetch their rendering bundle from the CDN, pinned to the exact `@roxyapi/ui` release the package was built against, so a lockfile pins your runtime too. Behind a strict Content-Security-Policy, an air-gapped network, or offline development nothing will render, and every component shows a visible `Roxy UI script load failed` error rather than failing quietly.
|
|
319
319
|
|
|
320
320
|
Either allowlist `cdn.jsdelivr.net` in `script-src`, or serve the bundle yourself. Copy `node_modules/@roxyapi/ui/dist/cdn/` onto your own origin and call the loader ONCE at app entry, before any component mounts:
|
|
321
321
|
|
|
@@ -557,7 +557,7 @@ Rules for this pattern:
|
|
|
557
557
|
|
|
558
558
|
This is how the WordPress plugin renders: PHP fetches the response server-side, caches it, and writes the script into the page. The same shape works in any framework that emits HTML.
|
|
559
559
|
|
|
560
|
-
- Writing the tag itself in a React or Next.js file? Import `@roxyapi/ui-react/jsx` once anywhere in the project and every `roxy-*` tag is typed, with its attributes and their legal values. It is the raw-tag path, so it carries attributes only; a page that passes a response uses the
|
|
560
|
+
- Writing the tag itself in a React or Next.js file? Import `@roxyapi/ui-react/jsx` once anywhere in the project and every `roxy-*` tag is typed, with its attributes and their legal values. It is the raw-tag path, so it carries attributes only; a page that passes a response uses the React or Vue component instead, which sets `data` as a property.
|
|
561
561
|
|
|
562
562
|
## Localized responses
|
|
563
563
|
|
|
@@ -628,7 +628,7 @@ Per-element scope is supported:
|
|
|
628
628
|
|
|
629
629
|
Every visible aspect of the chart is driven by `--roxy-*` CSS custom properties on `:host`. Override any token on `:root`, on `:host`, or per element. Do not write Tailwind utility classes inside the components; the Shadow DOM boundary stops them at the door.
|
|
630
630
|
|
|
631
|
-
**One plain declaration is the whole override, including from inside a layer of your own.** The shipped defaults are declared at zero specificity and inside the `roxy` cascade layer, so `:root { --roxy-accent: #6d28d9 }` beats them in both modes, and so does the same line inside `@layer base`, which is where a framework maps its palette onto ours. Never reach for `html:root` or `!important`. If you link `tokens.css` after your own CSS, name the order once with `@layer roxy, base, components, utilities;`. And if your tokens are scoped to a
|
|
631
|
+
**One plain declaration is the whole override, including from inside a layer of your own.** The shipped defaults are declared at zero specificity and inside the `roxy` cascade layer, so `:root { --roxy-accent: #6d28d9 }` beats them in both modes, and so does the same line inside `@layer base`, which is where a framework maps its palette onto ours. Never reach for `html:root` or `!important`. If you link `tokens.css` after your own CSS, name the order once with `@layer roxy, base, components, utilities;`. And if your tokens are scoped to a container element rather than to `:root`, write the mode on that same container element (`data-theme="light"` or `"dark"`), because every token you did not override is still decided at the document root by the visitor OS.
|
|
632
632
|
|
|
633
633
|
## Choosing what a component renders
|
|
634
634
|
|
|
@@ -663,7 +663,7 @@ Both are off by default. `hide-sections` takes a comma-separated list, is case-i
|
|
|
663
663
|
|
|
664
664
|
| part | What it names |
|
|
665
665
|
|---|---|
|
|
666
|
-
| `card` | The component's own card or
|
|
666
|
+
| `card` | The component's own card or container root |
|
|
667
667
|
| `header` | The heading row (title, meta, score) |
|
|
668
668
|
| `chart` | The graphic: wheel, map, bodygraph, bar set, hexagram figure, card art |
|
|
669
669
|
| `legend` | The key to the chart |
|
package/README.md
CHANGED
|
@@ -398,7 +398,7 @@ export function ToolWidget({ toolName, output }: { toolName: string; output: str
|
|
|
398
398
|
|
|
399
399
|
A compact tool result is decoded for you, and a name a host prefixed with its server (`roxy_tarot:post_tarot_daily`) resolves the same as a bare one. Full recipe, with the vendor connectors and the Vercel AI SDK: <https://roxyapi.com/docs/tutorials/ai-chat-widgets>. Runnable page: [examples/vanilla/tool-result.html](examples/vanilla/tool-result.html).
|
|
400
400
|
|
|
401
|
-
**The lookup also ships on its own path**, `@roxyapi/ui/tool-component` and the same subpath on both
|
|
401
|
+
**The lookup also ships on its own path**, `@roxyapi/ui/tool-component` and the same subpath on both framework packages, for a module that decides WHICH component to render and never renders one: a server component, a route handler, a worker. It carries `componentForTool`, `expandCompact` and the name table, and no elements, so nothing in that file pulls in the library.
|
|
402
402
|
|
|
403
403
|
```ts
|
|
404
404
|
import { componentForTool } from '@roxyapi/ui-react/tool-component';
|
|
@@ -462,7 +462,7 @@ export default function Page() {
|
|
|
462
462
|
}
|
|
463
463
|
```
|
|
464
464
|
|
|
465
|
-
One import anywhere in the project types the tags everywhere in it. The typings carry attributes only, which is what markup can carry: a page that passes a response uses the
|
|
465
|
+
One import anywhere in the project types the tags everywhere in it. The typings carry attributes only, which is what markup can carry: a page that passes a response uses the React or Vue component, which sets `data` as a property. Your `tsconfig.json` needs `moduleResolution` on `bundler`, `node16` or `nodenext`, because the older `node10` resolution ignores the package export map.
|
|
466
466
|
|
|
467
467
|
## Most-used components per domain
|
|
468
468
|
|
|
@@ -941,7 +941,7 @@ Every file a page loads ships in the package `dist` folder, and each [GitHub rel
|
|
|
941
941
|
|
|
942
942
|
## Theming
|
|
943
943
|
|
|
944
|
-
Every component takes every colour, size, radius, space and font from `--roxy-*` CSS custom properties, and most of them derive from a handful of bases, so restyle through the tokens and never by overriding the internals of a component. Override globally on `:root` or per element. Light + dark defaults, container queries for responsive layouts at 320px and up. Every component loads the default tokens when it connects, from npm and the CDN alike, and your own declarations always win over the defaults: they are declared at zero specificity and inside the `roxy` cascade layer, so one plain line beats them in both modes, with no `!important` and no extra selector weight, and it works from inside a layer of your own. See [THEMING.md](https://github.com/RoxyAPI/ui/blob/main/packages/ui/THEMING.md) for the full token reference and for the one rule a page that scopes its theme to a
|
|
944
|
+
Every component takes every colour, size, radius, space and font from `--roxy-*` CSS custom properties, and most of them derive from a handful of bases, so restyle through the tokens and never by overriding the internals of a component. Override globally on `:root` or per element. Light + dark defaults, container queries for responsive layouts at 320px and up. Every component loads the default tokens when it connects, from npm and the CDN alike, and your own declarations always win over the defaults: they are declared at zero specificity and inside the `roxy` cascade layer, so one plain line beats them in both modes, with no `!important` and no extra selector weight, and it works from inside a layer of your own. See [THEMING.md](https://github.com/RoxyAPI/ui/blob/main/packages/ui/THEMING.md) for the full token reference and for the one rule a page that scopes its theme to a container element has to know.
|
|
945
945
|
|
|
946
946
|
```css
|
|
947
947
|
:root {
|
package/THEMING.md
CHANGED
|
@@ -33,7 +33,7 @@ Layer order is decided by the order the names are first seen, and `roxy` is regi
|
|
|
33
33
|
@layer roxy, base, components, utilities;
|
|
34
34
|
```
|
|
35
35
|
|
|
36
|
-
**If you cannot own `:root`, say which mode you are in on the element you scope to.** A multi-tenant page, or a framework that owns `<html>`, puts its tokens on a
|
|
36
|
+
**If you cannot own `:root`, say which mode you are in on the element you scope to.** A multi-tenant page, or a framework that owns `<html>`, puts its tokens on a container element instead. Custom properties inherit, so that works for every token you set. Every token you do NOT set still comes from `:root`, where the default is chosen by the visitor operating system, and a light page opened on a dark phone then draws the pale status inks onto a near-white card. Declare the mode on the same container element and the whole set follows it:
|
|
37
37
|
|
|
38
38
|
```html
|
|
39
39
|
<div class="my-site" data-theme="light">
|
|
@@ -217,7 +217,7 @@ Three opt-in mechanisms work out of the box, on the CDN and the npm path alike,
|
|
|
217
217
|
|
|
218
218
|
Tokens set on the `:root` / `.dark` / `[data-theme]` light-DOM element inherit through the shadow boundary into every component, so a `.dark` class anywhere above a component themes it. Per-element scope works too: `<roxy-natal-chart data-theme="dark">` runs one chart in dark on an otherwise light page.
|
|
219
219
|
|
|
220
|
-
"System preference: nothing to do" holds only while the mode is a whole-document question. A page that scopes its theme to a
|
|
220
|
+
"System preference: nothing to do" holds only while the mode is a whole-document question. A page that scopes its theme to a container element is the exception, and it is the common one on a multi-tenant site: the system preference still decides every token that container does not set. Declare the mode on that container element, as the host contract above shows.
|
|
221
221
|
|
|
222
222
|
### Map Tailwind tokens
|
|
223
223
|
|
|
@@ -251,7 +251,7 @@ If you used the shadcn registry path, this bridge installs automatically and rea
|
|
|
251
251
|
|
|
252
252
|
### Per-domain accent presets
|
|
253
253
|
|
|
254
|
-
One accent per domain, so a multi-domain page reads as related products. Scope an accent to a
|
|
254
|
+
One accent per domain, so a multi-domain page reads as related products. Scope an accent to a container element and every component inside it picks it up.
|
|
255
255
|
|
|
256
256
|
Every ink value below is measured against the default page background: each passes WCAG AA (4.5:1) in **both** light and dark. `--roxy-accent` alone is enough, since the ink and the ring derive from it; the ink column is a hand-tuned shade for accent-coloured _text_ when you want one.
|
|
257
257
|
|