Skip to content

docs(Dropdown): Searchable single select page (current implementation)#3406

Open
rivka-ungar wants to merge 4 commits into
masterfrom
docs/searchable-single-select-current-examples
Open

docs(Dropdown): Searchable single select page (current implementation)#3406
rivka-ungar wants to merge 4 commits into
masterfrom
docs/searchable-single-select-current-examples

Conversation

@rivka-ungar

Copy link
Copy Markdown
Contributor

Purpose

Adds the same Searchable single select stories and accessibility page that exist on the fix branch (fix/single-searchable-dropdown-a11y-selected-value), but on a branch off master with the current component implementation unchanged.

This lets us deploy/compare the identical examples on two branches:

  • This branch (master-based): current behavior — selected value shown as a visual overlay.
  • Fix branch: new behavior — selected value lives inside the input.

The story files are byte-identical to the fix branch, so any rendering difference between the two Storybooks is due solely to the component change, making the before/after easy to compare.

Note

This branch contains only the docs/stories — no component changes. The page's prose describes the target behavior; the live examples render the current implementation, which is exactly the comparison point.

🤖 Generated with Claude Code

…tion)

Adds the same Searchable single select stories and accessibility page as the
fix branch, on a branch off master, so the identical examples can be compared
against the current implementation.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@rivka-ungar rivka-ungar requested a review from a team as a code owner June 11, 2026 11:27
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0)

Grey Divider


Action required

1. Unlabeled combobox examples ✓ Resolved 🐞 Bug ⛨ Security
Description
New stories render searchable Dropdowns without label, aria-label, or inputAriaLabel, so the
combobox can end up without a meaningful accessible name. This contradicts the page’s own
“Placeholder is not a label” guidance and can fail a11y checks.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[R407-414]

+            <Dropdown
+              id="searchable-single-groups"
+              options={groupedOptions}
+              searchable
+              placeholder="Search a team"
+              maxMenuHeight={200}
+              clearAriaLabel="Clear"
+            />
Evidence
The WithGroups and CustomFilterAndNoOptions stories create searchable Dropdowns without any naming
props. In the core searchable trigger, aria-labelledby is only applied when label exists and
otherwise it relies on inputAriaLabel, so these examples do not provide a meaningful accessible
name.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-445]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-559]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[35-46]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Some new searchable Dropdown examples omit `label` / `aria-label` / `inputAriaLabel`. For searchable dropdowns, the accessible name is only correctly wired when one of these naming props is provided; otherwise the combobox can be effectively unnamed.
### Issue Context
This is an accessibility-focused docs page, and the MDX explicitly states placeholder is not a label, so the examples should model best practice.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-448]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-564]
### What to change
- For each unlabeled searchable Dropdown, add either:
- `label="…"` (preferred), or
- `aria-label="…"` / `inputAriaLabel="…"` when a visible label isn’t desired.
- Ensure each example’s naming matches the visible helper text/context (avoid relying on surrounding `<Text>` as a label).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. Docs mismatch current behavior ✓ Resolved 🐞 Bug ≡ Correctness
Description
The new searchable single-select accessibility page/stories state the selected label is written into
the combobox input and the overlay is removed, but the current Dropdown still renders the selected
item as an overlay when !inputValue && selectedItem. This makes the new docs and story
explanations incorrect for the current implementation on this branch.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[R18-36]

+## What changed
+
+Previously, selecting an option in a searchable single select **cleared the input** and rendered the selected label as a **visual overlay** on top of the empty field. Because screen readers read the input's value — not the overlay — a field with a selection was announced as blank.
+
+The behavior was changed so the selected option's label is now set as the **value of the input itself**, and the overlay was removed.
+
+| Aspect                              | Before                                  | After                       |
+| ----------------------------------- | --------------------------------------- | --------------------------- |
+| Input value after selecting         | Empty                                   | The selected label          |
+| How the selection is shown          | Visual overlay over an empty input      | Inside the input            |
+| Screen reader on focus              | _"…, blank"_                            | _"…, the selected label"_   |
+| `defaultValue` / `value` on mount   | Shown via the overlay                   | Shown in the input          |
+| Collapsed selected value            | Rich (icon / avatar / `valueRenderer`)  | Text-only                   |
+
+This is scoped to **searchable single select**. Non-searchable single select and multi-select are unchanged.
+
+## The core behavior: the selected value lives inside the input
+
+When an option is selected, its label is set as the **value of the `<input role="combobox">`**. It is not painted as a separate visual layer on top of an empty field.
Evidence
The MDX and story text claim the overlay is removed and the selected label becomes the input value,
but the current core implementation still renders an overlay (styles.selectedItem) whenever there
is a selected item and inputValue is empty; the input value itself is driven by inputValue and
placeholder is cleared when a selection exists.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-36]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
packages/core/src/components/Dropdown/components/Trigger/SingleSelectTrigger.tsx[11-67]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[9-57]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new MDX page and story descriptions assert the “selected value in input / no overlay” behavior, but the current component still uses an overlay for searchable single select when the input value is empty. This causes the docs page to describe behavior users will not observe in this Storybook build.
### Issue Context
This PR intentionally adds docs/stories only, but as written the page reads like authoritative documentation for the current component.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-56]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[331-377]
### What to change
- Either (A) update prose to match the current implementation (overlay + rich collapsed value), or (B) add an explicit banner/note near the top explaining that this branch intentionally shows the pre-fix behavior and the text describes the target/fix behavior.
- Ensure any inline explanatory text in stories (e.g., WithDefaultValue / WithValueRenderer) is consistent with whichever approach you choose.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Previous review results

Review updated until commit 7a706d3

Results up to commit ea3ee33


🐞 Bugs (0) 📘 Rule violations (0)


Action required
1. Unlabeled combobox examples ✓ Resolved 🐞 Bug ⛨ Security
Description
New stories render searchable Dropdowns without label, aria-label, or inputAriaLabel, so the
combobox can end up without a meaningful accessible name. This contradicts the page’s own
“Placeholder is not a label” guidance and can fail a11y checks.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[R407-414]

+            <Dropdown
+              id="searchable-single-groups"
+              options={groupedOptions}
+              searchable
+              placeholder="Search a team"
+              maxMenuHeight={200}
+              clearAriaLabel="Clear"
+            />
Evidence
The WithGroups and CustomFilterAndNoOptions stories create searchable Dropdowns without any naming
props. In the core searchable trigger, aria-labelledby is only applied when label exists and
otherwise it relies on inputAriaLabel, so these examples do not provide a meaningful accessible
name.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-445]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-559]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[35-46]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Some new searchable Dropdown examples omit `label` / `aria-label` / `inputAriaLabel`. For searchable dropdowns, the accessible name is only correctly wired when one of these naming props is provided; otherwise the combobox can be effectively unnamed.
### Issue Context
This is an accessibility-focused docs page, and the MDX explicitly states placeholder is not a label, so the examples should model best practice.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-448]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-564]
### What to change
- For each unlabeled searchable Dropdown, add either:
- `label="…"` (preferred), or
- `aria-label="…"` / `inputAriaLabel="…"` when a visible label isn’t desired.
- Ensure each example’s naming matches the visible helper text/context (avoid relying on surrounding `<Text>` as a label).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended
2. Docs mismatch current behavior ✓ Resolved 🐞 Bug ≡ Correctness
Description
The new searchable single-select accessibility page/stories state the selected label is written into
the combobox input and the overlay is removed, but the current Dropdown still renders the selected
item as an overlay when !inputValue && selectedItem. This makes the new docs and story
explanations incorrect for the current implementation on this branch.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[R18-36]

+## What changed
+
+Previously, selecting an option in a searchable single select **cleared the input** and rendered the selected label as a **visual overlay** on top of the empty field. Because screen readers read the input's value — not the overlay — a field with a selection was announced as blank.
+
+The behavior was changed so the selected option's label is now set as the **value of the input itself**, and the overlay was removed.
+
+| Aspect                              | Before                                  | After                       |
+| ----------------------------------- | --------------------------------------- | --------------------------- |
+| Input value after selecting         | Empty                                   | The selected label          |
+| How the selection is shown          | Visual overlay over an empty input      | Inside the input            |
+| Screen reader on focus              | _"…, blank"_                            | _"…, the selected label"_   |
+| `defaultValue` / `value` on mount   | Shown via the overlay                   | Shown in the input          |
+| Collapsed selected value            | Rich (icon / avatar / `valueRenderer`)  | Text-only                   |
+
+This is scoped to **searchable single select**. Non-searchable single select and multi-select are unchanged.
+
+## The core behavior: the selected value lives inside the input
+
+When an option is selected, its label is set as the **value of the `<input role="combobox">`**. It is not painted as a separate visual layer on top of an empty field.
Evidence
The MDX and story text claim the overlay is removed and the selected label becomes the input value,
but the current core implementation still renders an overlay (styles.selectedItem) whenever there
is a selected item and inputValue is empty; the input value itself is driven by inputValue and
placeholder is cleared when a selection exists.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-36]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
packages/core/src/components/Dropdown/components/Trigger/SingleSelectTrigger.tsx[11-67]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[9-57]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new MDX page and story descriptions assert the “selected value in input / no overlay” behavior, but the current component still uses an overlay for searchable single select when the input value is empty. This causes the docs page to describe behavior users will not observe in this Storybook build.
### Issue Context
This PR intentionally adds docs/stories only, but as written the page reads like authoritative documentation for the current component.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-56]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[331-377]
### What to change
- Either (A) update prose to match the current implementation (overlay + rich collapsed value), or (B) add an explicit banner/note near the top explaining that this branch intentionally shows the pre-fix behavior and the text describes the target/fix behavior.
- Ensure any inline explanatory text in stories (e.g., WithDefaultValue / WithValueRenderer) is consistent with whichever approach you choose.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Results up to commit N/A


🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0)


Action required
1. Unlabeled combobox examples 🐞 Bug ⛨ Security
Description
New stories render searchable Dropdowns without label, aria-label, or inputAriaLabel, so the
combobox can end up without a meaningful accessible name. This contradicts the page’s own
“Placeholder is not a label” guidance and can fail a11y checks.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[R407-414]

+            <Dropdown
+              id="searchable-single-groups"
+              options={groupedOptions}
+              searchable
+              placeholder="Search a team"
+              maxMenuHeight={200}
+              clearAriaLabel="Clear"
+            />
Evidence
The WithGroups and CustomFilterAndNoOptions stories create searchable Dropdowns without any naming
props. In the core searchable trigger, aria-labelledby is only applied when label exists and
otherwise it relies on inputAriaLabel, so these examples do not provide a meaningful accessible
name.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-445]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-559]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[35-46]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Some new searchable Dropdown examples omit `label` / `aria-label` / `inputAriaLabel`. For searchable dropdowns, the accessible name is only correctly wired when one of these naming props is provided; otherwise the combobox can be effectively unnamed.
### Issue Context
This is an accessibility-focused docs page, and the MDX explicitly states placeholder is not a label, so the examples should model best practice.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[379-448]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[525-564]
### What to change
- For each unlabeled searchable Dropdown, add either:
- `label="…"` (preferred), or
- `aria-label="…"` / `inputAriaLabel="…"` when a visible label isn’t desired.
- Ensure each example’s naming matches the visible helper text/context (avoid relying on surrounding `<Text>` as a label).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended
2. Docs mismatch current behavior ✓ Resolved 🐞 Bug ≡ Correctness
Description
The new searchable single-select accessibility page/stories state the selected label is written into
the combobox input and the overlay is removed, but the current Dropdown still renders the selected
item as an overlay when !inputValue && selectedItem. This makes the new docs and story
explanations incorrect for the current implementation on this branch.
Code

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[R18-36]

+## What changed
+
+Previously, selecting an option in a searchable single select **cleared the input** and rendered the selected label as a **visual overlay** on top of the empty field. Because screen readers read the input's value — not the overlay — a field with a selection was announced as blank.
+
+The behavior was changed so the selected option's label is now set as the **value of the input itself**, and the overlay was removed.
+
+| Aspect                              | Before                                  | After                       |
+| ----------------------------------- | --------------------------------------- | --------------------------- |
+| Input value after selecting         | Empty                                   | The selected label          |
+| How the selection is shown          | Visual overlay over an empty input      | Inside the input            |
+| Screen reader on focus              | _"…, blank"_                            | _"…, the selected label"_   |
+| `defaultValue` / `value` on mount   | Shown via the overlay                   | Shown in the input          |
+| Collapsed selected value            | Rich (icon / avatar / `valueRenderer`)  | Text-only                   |
+
+This is scoped to **searchable single select**. Non-searchable single select and multi-select are unchanged.
+
+## The core behavior: the selected value lives inside the input
+
+When an option is selected, its label is set as the **value of the `<input role="combobox">`**. It is not painted as a separate visual layer on top of an empty field.
Evidence
The MDX and story text claim the overlay is removed and the selected label becomes the input value,
but the current core implementation still renders an overlay (styles.selectedItem) whenever there
is a selected item and inputValue is empty; the input value itself is driven by inputValue and
placeholder is cleared when a selection exists.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-36]
packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
packages/core/src/components/Dropdown/components/Trigger/SingleSelectTrigger.tsx[11-67]
packages/core/src/components/Dropdown/components/Trigger/DropdownInput.tsx[9-57]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new MDX page and story descriptions assert the “selected value in input / no overlay” behavior, but the current component still uses an overlay for searchable single select when the input value is empty. This causes the docs page to describe behavior users will not observe in this Storybook build.
### Issue Context
This PR intentionally adds docs/stories only, but as written the page reads like authoritative documentation for the current component.
### Fix Focus Areas
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx[18-56]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[173-190]
- packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx[331-377]
### What to change
- Either (A) update prose to match the current implementation (overlay + rich collapsed value), or (B) add an explicit banner/note near the top explaining that this branch intentionally shows the pre-fix behavior and the text describes the target/fix behavior.
- Ensure any inline explanatory text in stories (e.g., WithDefaultValue / WithValueRenderer) is consistent with whichever approach you choose.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Qodo Logo

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

PR Summary by Qodo

docs(Dropdown): Add searchable single-select Storybook page for current impl
📝 Documentation 🕐 10-20 Minutes

Grey Divider

Walkthroughs

Description
• Add Storybook MDX accessibility page for searchable single-select Dropdown examples.
• Introduce a matching stories suite to compare current vs fix-branch rendering.
• Touch SingleSelectTrigger with a comment to ensure Chromatic publishes preview builds.
Diagram
graph TD
  A["MDX docs page"] --> B["Stories (TSX)"] --> C["Storybook build"] --> D["Dropdown component"] --> E["SingleSelectTrigger"]
  C --> F{{"Chromatic preview"}}
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Feature-flag the trigger behavior and document both modes in one Storybook
  • ➕ Single source of truth for docs/stories
  • ➕ Easier long-term maintenance; no duplicate pages across branches
  • ➕ Allows side-by-side comparison within one deployment
  • ➖ Introduces conditional logic/flags in core component code
  • ➖ Requires careful release/cleanup to avoid permanent flags
2. Keep docs only on the fix branch and rely on Chromatic baseline comparisons
  • ➕ Avoids adding/maintaining duplicate docs on master-based branch
  • ➕ Chromatic can highlight visual diffs against existing baselines
  • ➖ Harder for reviewers to manually compare two identical story sets across branches
  • ➖ Baseline setup may not mirror the desired before/after narrative
3. Create a single story that demonstrates both renderings via controlled props/mocks
  • ➕ Comparison is localized and explicit (A/B in one story)
  • ➕ No need for a separate MDX page duplication
  • ➖ May require non-trivial mocking or API surface changes if behavior is internal
  • ➖ Could diverge from real-world usage

Recommendation: For a short-lived, reviewer-focused before/after comparison, duplicating the example set on a master-based branch is a pragmatic approach because it isolates rendering differences to the component implementation. If these docs are expected to persist, prefer a single Storybook with a temporary feature flag or an explicit A/B story to avoid ongoing duplication and drift.

Grey Divider

File Changes

Documentation (3)
SingleSelectTrigger.tsx Add clarifying comment to SingleSelectTrigger (no behavior change) +1/-0

Add clarifying comment to SingleSelectTrigger (no behavior change)

• Adds a brief comment describing SingleSelectTrigger’s role for single-select dropdowns. This also forces a detectable @vibe/core change so CI/Chromatic publishes an updated preview for the new docs examples.

packages/core/src/components/Dropdown/components/Trigger/SingleSelectTrigger.tsx


DropdownSearchableSingleSelect.mdx Add MDX accessibility page for searchable single-select Dropdown +32/-0

Add MDX accessibility page for searchable single-select Dropdown

• Introduces a Storybook MDX page that composes five example canvases (Overview, default value, icons/avatars, end elements, valueRenderer). Provides import guidance and serves as the comparison surface for current vs fix-branch behavior.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.mdx


DropdownSearchableSingleSelect.stories.tsx Add searchable single-select Dropdown stories covering core variants +230/-0

Add searchable single-select Dropdown stories covering core variants

• Adds a new Storybook stories file for searchable single-select Dropdown, including baseline usage plus defaultValue, start/end elements, and a custom valueRenderer. Configures docs/liveEdit parameters and includes assets (avatars) and icons used by the examples.

packages/docs/src/pages/components/Dropdown/DropdownSearchableSingleSelect.stories.tsx


Grey Divider

Qodo Logo

Keep the same examples and section titles but remove the descriptive prose
and in-story captions that describe the new (fix-branch) behavior, so this
master-based page just shows the current dropdowns for comparison.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Code Review by Qodo

Grey Divider

New Review Started

This review has been superseded by a new analysis

Grey Divider

Qodo Logo

Keep only the five examples the new page documents (Overview, default value,
icons & avatars, end elements, valueRenderer); remove the extra examples so
the two pages line up one-to-one for comparison.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Code review by qodo was updated up to the latest commit ea3ee33

Touches @vibe/core so CI detects a package change and publishes the Chromatic
Storybook preview for the docs examples.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Code review by qodo was updated up to the latest commit 7a706d3

@github-actions

Copy link
Copy Markdown
Contributor

📦 Bundle Size Analysis

✅ No bundle size changes detected.

Unchanged Components
Component Base PR Diff
@vibe/button 17.35KB 17.28KB -75B 🟢
@vibe/clickable 5.96KB 5.97KB +19B 🔺
@vibe/dialog 52.22KB 52.18KB -47B 🟢
@vibe/icon-button 66.1KB 66.08KB -29B 🟢
@vibe/icon 12.89KB 12.87KB -25B 🟢
@vibe/layer 2.96KB 2.96KB 0B ➖
@vibe/layout 9.82KB 9.82KB -6B 🟢
@vibe/loader 5.63KB 5.65KB +13B 🔺
@vibe/tooltip 61.32KB 61.29KB -27B 🟢
@vibe/typography 63.5KB 63.46KB -42B 🟢
Accordion 6.3KB 6.29KB -15B 🟢
AccordionItem 66.53KB 66.46KB -73B 🟢
AlertBanner 70.93KB 70.81KB -124B 🟢
AlertBannerButton 18.79KB 18.78KB -11B 🟢
AlertBannerLink 15.29KB 15.25KB -39B 🟢
AlertBannerText 64KB 63.93KB -72B 🟢
AttentionBox 74.31KB 74.28KB -37B 🟢
Avatar 66.75KB 66.77KB +26B 🔺
AvatarGroup 93.28KB 93.33KB +55B 🔺
Badge 43.22KB 43.21KB -10B 🟢
BreadcrumbItem 64.69KB 64.72KB +26B 🔺
BreadcrumbMenu 68.61KB 68.62KB +6B 🔺
BreadcrumbMenuItem 77.15KB 77.04KB -111B 🟢
BreadcrumbsBar 5.68KB 5.69KB +7B 🔺
ButtonGroup 68.32KB 68.39KB +64B 🔺
Checkbox 66.87KB 66.94KB +70B 🔺
Chips 75.11KB 75.03KB -83B 🟢
ColorPicker 74.45KB 74.43KB -19B 🟢
ColorPickerContent 73.78KB 73.83KB +49B 🔺
Combobox 84.1KB 84.03KB -71B 🟢
Counter 42.19KB 42.23KB +35B 🔺
DatePicker 112.51KB 112.35KB -165B 🟢
Divider 5.45KB 5.44KB -10B 🟢
Dropdown 95.26KB 95.21KB -48B 🟢
EditableHeading 66.59KB 66.65KB +57B 🔺
EditableText 66.48KB 66.54KB +60B 🔺
EmptyState 70.52KB 70.42KB -100B 🟢
ExpandCollapse 66.31KB 66.24KB -70B 🟢
FormattedNumber 5.82KB 5.84KB +14B 🔺
GridKeyboardNavigationContext 4.65KB 4.65KB -4B 🟢
HiddenText 5.4KB 5.39KB -13B 🟢
Info 72.15KB 72.06KB -95B 🟢
Label 68.69KB 68.67KB -25B 🟢
Link 14.89KB 14.88KB -11B 🟢
List 72.98KB 72.87KB -110B 🟢
ListItem 65.5KB 65.53KB +30B 🔺
ListItemAvatar 66.92KB 66.92KB -6B 🟢
ListItemIcon 14.02KB 14.02KB -4B 🟢
ListTitle 65.03KB 65.06KB +32B 🔺
Menu 8.64KB 8.65KB +15B 🔺
MenuDivider 5.56KB 5.56KB -1B 🟢
MenuGridItem 7.16KB 7.19KB +36B 🔺
MenuItem 76.95KB 76.97KB +17B 🔺
MenuItemButton 70.04KB 70.15KB +118B 🔺
MenuTitle 65.39KB 65.27KB -117B 🟢
MenuButton 66.15KB 66.21KB +65B 🔺
Modal 79.11KB 79.13KB +18B 🔺
ModalContent 4.72KB 4.71KB -1B 🟢
ModalHeader 65.86KB 65.79KB -76B 🟢
ModalMedia 7.51KB 7.47KB -37B 🟢
ModalFooter 67.76KB 67.7KB -64B 🟢
ModalFooterWizard 68.69KB 68.61KB -86B 🟢
ModalBasicLayout 8.93KB 8.94KB +3B 🔺
ModalMediaLayout 8.07KB 8.06KB -8B 🟢
ModalSideBySideLayout 6.3KB 6.31KB +12B 🔺
MultiStepIndicator 52.98KB 52.93KB -50B 🟢
NumberField 72.84KB 72.85KB +16B 🔺
ProgressBar 7.32KB 7.34KB +19B 🔺
RadioButton 65.88KB 65.95KB +67B 🔺
Search 70.68KB 70.71KB +25B 🔺
Skeleton 5.99KB 6.01KB +18B 🔺
Slider 73.82KB 73.81KB -15B 🟢
SplitButton 66.52KB 66.53KB +8B 🔺
SplitButtonMenu 8.8KB 8.78KB -23B 🟢
Steps 71.45KB 71.34KB -118B 🟢
Table 7.24KB 7.24KB +2B 🔺
TableBody 66.79KB 66.78KB -15B 🟢
TableCell 65.31KB 65.19KB -132B 🟢
TableContainer 5.31KB 5.32KB +3B 🔺
TableHeader 5.63KB 5.63KB +3B 🔺
TableHeaderCell 72.22KB 72.17KB -46B 🟢
TableRow 5.55KB 5.54KB -5B 🟢
TableRowMenu 68.84KB 68.8KB -37B 🟢
TableVirtualizedBody 71.42KB 71.43KB +8B 🔺
Tab 64.02KB 64.05KB +37B 🔺
TabList 8.9KB 8.85KB -54B 🟢
TabPanel 5.31KB 5.29KB -21B 🟢
TabPanels 5.83KB 5.84KB +6B 🔺
TabsContext 5.48KB 5.51KB +29B 🔺
TextArea 66.37KB 66.39KB +12B 🔺
TextField 69.4KB 69.4KB -5B 🟢
TextWithHighlight 64.4KB 64.26KB -142B 🟢
ThemeProvider 4.36KB 4.36KB -1B 🟢
Tipseen 71.21KB 71.1KB -118B 🟢
TipseenContent 71.72KB 71.71KB -16B 🟢
TipseenMedia 71.36KB 71.38KB +21B 🔺
TipseenWizard 73.92KB 73.86KB -60B 🟢
Toast 74.01KB 74.08KB +64B 🔺
ToastButton 18.6KB 18.61KB +7B 🔺
ToastLink 15.08KB 15.09KB +17B 🔺
Toggle 66.68KB 66.64KB -38B 🟢
TransitionView 5.44KB 5.44KB -4B 🟢
VirtualizedGrid 12.54KB 12.53KB -10B 🟢
VirtualizedList 12.29KB 12.28KB -4B 🟢
List (Next) 8.16KB 8.15KB -10B 🟢
ListItem (Next) 69.88KB 69.94KB +58B 🔺
ListTitle (Next) 65.36KB 65.34KB -16B 🟢

📊 Summary:

  • Total Base Size: 4.75MB
  • Total PR Size: 4.75MB
  • Total Difference: 1.6KB

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.

1 participant