Skip to content

Update dependency @whatsaaaa/design-system to ^0.13.0 - #102

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/@whatsaaaa-packages
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/@whatsaaaa-packages

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@whatsaaaa/design-system ^0.8.2 → ^0.13.0 age confidence

Release Notes

whatsaaaa/design-system (@​whatsaaaa/design-system)

v0.13.0

Compare Source

Minor Changes
  • #​62 0e4878d Thanks @​whatsaaaa! - Two more component specs, both drafts: checkbox and radio-group, in their list look and Nuxt UI's five sizes. In forced colors each keeps the edge of its box or circle, and a checked one its fill and its mark. The checkbox is checked, indeterminate or neither, with its label, description, required mark and error; the radio group is a legend over its options. Each has a page in the style guide, drawn from its file, and records what ui-vue draws today and where it does not meet the spec yet, such as a disabled checked box in the interactive fill.

    The component tier gains the choice group, what the two share: --ws-choice-control-size-<size>, the side of the box or the circle at each size, 14 to 24 px; its color --ws-choice-control-bg and edge --ws-choice-control-border-<rest|hover|invalid|disabled>; the fill and the mark of a checked or an indeterminate one, --ws-choice-indicator-<bg|icon>-<checked|indeterminate|disabled>; and an option's label and description, --ws-choice-label-text-<rest|disabled> and --ws-choice-description-text-<rest|disabled>. New semantic sizes for it: --ws-size-check-xs, -sm, -lg and -xl, 14, 16, 22 and 24 px, and --ws-size-tick-sm and -lg, the tick of 12 and 18 px. The space page of the style guide lists them.

    The testing helper compares an indeterminate example with its example at rest in forced colors too, and compares the two examples whole where the state draws a part the example at rest does not, such as a checked box's fill. Where an example has several elements of one slot, such as a group's options, it measures the first that draws the part. No existing token, style or spec changes.

  • #​67 b684f51 Thanks @​whatsaaaa! - Three more component specs, all drafts: select, select-menu and modal, each with its page in the style guide. A select and a select menu are a field, as the input's, in Nuxt UI's five sizes, whose list opens on a panel; a select menu's list has a search at its top. A modal is a window over the page dimmed in its own color, with a header bar as tall as the tab bar, a body and a footer of actions. Their implementations record what ui-vue draws today and where it does not meet them yet.

    The component tier gains the overlay group, for what a select's list and a modal's window share: --ws-overlay-bg, the edge --ws-overlay-border and --ws-overlay-border-width, and for each the radius and the padding, --ws-overlay-list-radius, --ws-overlay-list-padding, --ws-overlay-window-radius and --ws-overlay-window-padding. The edge is the field border, which reads at 3:1 on the panel and on the page. An overlay has no shadow, as nothing in the system does, and its specs say box-shadow: none.

    A spec row can set padding-block, min-height, max-width, box-shadow, text-transform and the line under a part, border-block-end-style, -width and -color, and the testing helper compares border-block-end-color as a color. An implementation's part map can name a slot inside another where one slot draws two parts, base leadingIcon, the icon of a select menu's trigger and not of the search in its list. The open state's examples draw their list or window in place, inside the example, and a select's example wraps the select itself, never its form field.

v0.12.0

Compare Source

Minor Changes
  • #​52 b5d9212 Thanks @​whatsaaaa! - @whatsaaaa/design-system/stylelint, the token lint rules as a stylelint config, so a project extends it in place of keeping its own copy: a hex value, a named color or a color written with one of the functions rgb, rgba, hsl, hsla, oklch, oklab, lab, lch and hwb is an error, and so is a variable that nothing defines, checked against the tokens.css of the version installed, the component tier included, wherever the linter runs. It extends stylelint-config-standard. stylelint, stylelint-config-standard and stylelint-value-no-unknown-custom-properties are optional peers that only this entry needs. docs/usage.md describes it in section 2. Nothing that exists changes.
Patch Changes
  • #​54 f0f5df4 Thanks @​whatsaaaa! - The input spec keeps a field's value and icons in their place when its edge widens in an error. Its padding rows were written for rest and so held a field with an error too, whose edge is control.border-width.invalid, 2 px, against 1 px at rest: a field whose value did not move measured 1 px less and failed at every size. The spec now has invalid rows for padding-inline-start and padding-inline-end at each size, with an icon on that side and without one, each the padding at rest less the extra edge, control.border-width.invalid less control.border-width.rest (11 px at md, 35 px past an icon), and a note that says so.

    An implementation's gallery shows, at every size, a field at rest and a field with an error each with its icons and without them, since the rows at rest no longer hold a field with an error. The style guide shows such a padding by its total and names what it takes away.

v0.11.0

Compare Source

Minor Changes
  • #​50 62febc0 Thanks @​whatsaaaa! - A row of a component spec can hold only where an example draws a part, "with": "leading-icon", or only where it does not, "without": "leading-icon", and a value can read tokens by their variables, as in calc(var(--ws-space-12) + var(--ws-control-icon-size-md) + var(--ws-control-gap-md)). The testing helper holds each example only to the rows whose condition it meets, and its coverage check asks that some example meet each one. The rows can also set padding-inline-start and padding-inline-end.

    The input spec uses them: its root padding-inline rows, which an input with an icon could never meet, are now padding-inline-start and padding-inline-end at each size, the field's padding without an icon on that side and the padding, the control's icon size and its gap with one (36 px at md). Its gallery contract adds input.outline.invalid.xs, .sm, .lg and .xl, so the error's size is checked at every size. An implementation's gallery shows those four examples, and at every size an example with each icon and one without it.

v0.10.0

Compare Source

Minor Changes
  • #​48 03dd6f5 Thanks @​whatsaaaa! - @whatsaaaa/design-system/testing, a Playwright helper that holds an implementation's gallery to the published component specs, whatever its framework. expectSpec(page, 'button', { implementation: 'ui-vue' }) checks, in both themes, that every example of the spec's gallery is on the page by its data-spec id and every row of the state table is drawn by an example; that each property of each part is its token's value, resolved inside the part so a part held in the other theme is measured in it; and that in forced colors each part with an edge keeps a border or an outline and a checked, current or selected example still looks unlike its example at rest. A hover, a pressed state and the focus are forced with data-demo, never with the pointer. checkSpec returns the failures in place of failing, and specNames and loadSpec read the specs. @playwright/test is an optional peer that only this entry needs. docs/usage.md describes it in section 12. Nothing that exists changes.

v0.9.0

Compare Source

Minor Changes
  • #​44 f4a7bbe Thanks @​whatsaaaa! - Component specs: what every implementation of a component draws alike, as data. specs/<component>.spec.json, in the package as @whatsaaaa/design-system/specs/button.spec.json, checked against specs/spec.schema.json, names a component's parts, kinds, sizes and states, its state table (for each kind, state and part, the token each CSS property takes), its keys and accessibility rules, how each implementation maps onto it and where it does not meet it yet, and the examples its gallery shows by data-spec id. The first two are drafts: button, in the kinds primary, secondary, ghost, quiet and danger, an outline in both themes, in the five sizes, and input, the field with its label, help and error. The style guide has a page for each, drawn from its file, in a components section next to the styles, and docs/usage.md explains specs and the tier in section 12.

    The component tier gains the button group, the colors of each kind in each state: --ws-button-<kind>-<bg|border|text>-<state>, such as --ws-button-primary-bg-hover, and --ws-button-text-disabled and --ws-button-border-disabled. Nothing that exists changes.

  • #​41 4d39c4c Thanks @​whatsaaaa! - A component token tier: the names every implementation of a control reads alike, such as ui-vue on Nuxt UI or an app that draws its own fields. Its first two groups are --ws-control-*, the height, gap and icon size of a one-line control for each of Nuxt UI's five sizes, xs to xl, with its radius and border widths, and --ws-field-*, the colors of a text field, a select and a select menu and of every field's label, help, error and required mark. Each is an alias of a role or a measure, declared wherever a theme is chosen, so it follows a part of the page held in the other theme. They are in tokens/components/, in the resolver's new components set and in the token data, and not in Tailwind's theme: read them by name, as h-(--ws-control-height-md). docs/usage.md describes them, and docs/decisions.md says why the tier is thin.

    New semantic tokens for them: --ws-color-brand-text, the brand red as small text, love on dark and a darker love on light that reads at 4.5:1, for the required mark; --ws-size-control-xs, -sm, -lg and -xl, the heights of the other control sizes, 28, 32, 44 and 48 px; and --ws-size-icon-lg, 20 px, the icon of the two large sizes. In the Tailwind entry they are text-brand-text, h-control-sm and the like. Nothing that exists changes.

  • #​37 e977973 Thanks @​whatsaaaa! - Remove css/nuxt-ui.css, deprecated in 0.8.3. ui-vue now ships the stylesheet that points Nuxt UI's colors at the roles. An app on Nuxt UI imports @whatsaaaa/ui-vue/index.css, which brings it; an app that imported @whatsaaaa/design-system/css/nuxt-ui.css directly copies the file from 0.8.3 into its own stylesheets or moves to ui-vue.

v0.8.3

Compare Source

Patch Changes
  • #​33 0d94a82 Thanks @​whatsaaaa! - The current tab keeps its mark in forced colors, such as a Windows contrast theme. The browser dropped the bar over it, a shadow, and drew the edges every tab keeps for the current one on all of them, so the current tab looked like the others. In the tab bar of the terminal frame and in the docs theme it now has its bar and its number in the system's color of a selection and its edges in the text color, and the other tabs have no edges. Out of forced colors nothing changes. A page with the tab bar or a site on the docs theme takes this with no change of its own.

    css/nuxt-ui.css is deprecated and is removed in 0.9.0. It stays in 0.8.3 as it was. An app on Nuxt UI gets it from ui-vue, which @whatsaaaa/ui-vue/index.css brings. An app that imports @whatsaaaa/design-system/css/nuxt-ui.css directly copies the file from 0.8.3 into its own stylesheets and imports that copy in its place.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from 5b1d68a to fd5540e Compare November 18, 2026 03:42
@renovate renovate Bot changed the title Update dependency @whatsaaaa/design-system to v0.8.3 Update dependency @whatsaaaa/design-system to ^0.9.0 Nov 18, 2026
@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from fd5540e to 3ae8e22 Compare November 18, 2026 09:07
@renovate renovate Bot changed the title Update dependency @whatsaaaa/design-system to ^0.9.0 Update dependency @whatsaaaa/design-system to ^0.10.0 Nov 18, 2026
@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from 3ae8e22 to 20ae6ef Compare November 18, 2026 12:38
@renovate renovate Bot changed the title Update dependency @whatsaaaa/design-system to ^0.10.0 Update dependency @whatsaaaa/design-system to ^0.12.0 Nov 18, 2026
@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from 20ae6ef to 27e5826 Compare November 18, 2026 17:08
@renovate renovate Bot changed the title Update dependency @whatsaaaa/design-system to ^0.12.0 Update dependency @whatsaaaa/design-system to ^0.13.0 Nov 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants