@proyecto-viviana/ui 0.6.3 → 0.8.0-rc.1

package/LICENSE-APACHE-2.0

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2019 Adobe
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,91 @@
+Proyecto Viviana
+Copyright (c) Proyecto Viviana contributors
+
+Original Proyecto Viviana code is licensed under the MIT License (see LICENSE).
+This product also includes software that is derived from, or bundles, works
+licensed under the Apache License, Version 2.0 (see LICENSE-APACHE-2.0).
+The repository keeps a full, human-readable list of sourced, referenced, and
+inspired-by material at
+https://github.com/proyecto-viviana/ui/blob/main/CREDITS.md.
+
+================================================================================
+Apache-2.0 derived works (Adobe React Spectrum)
+================================================================================
+
+The following packages are SolidJS ports of, and contain code derived from,
+Adobe's React Spectrum project:
+
+  @proyecto-viviana/solid-stately         derived from  @react-stately/*
+  @proyecto-viviana/solidaria             derived from  @react-aria/*
+  @proyecto-viviana/solidaria-components  derived from  react-aria-components
+  @proyecto-viviana/solid-spectrum        derived from  @react-spectrum/s2
+  @proyecto-viviana/ui                    derived from  @react-spectrum/s2,
+                                           with local additions
+
+Original work:
+  React Spectrum
+  Copyright 2019 Adobe (and other contributors)
+  https://github.com/adobe/react-spectrum
+  Licensed under the Apache License, Version 2.0.
+
+Significant changes (Apache-2.0 section 4(b)): the source has been ported from
+React to SolidJS. APIs, the reactivity model (signals/stores in place of hooks),
+rendering, and behavior have been adapted to Solid's primitives.
+
+Some source files identify candidate or verified upstream mappings with an
+upstream notice or a "Ported from" / "Based on" reference. The repository is
+still auditing exact per-file mappings. This project-level notice does not claim
+that the per-file audit is complete.
+
+This product also depends on, or bundles for reference, the following Apache-2.0
+material from Adobe:
+
+  - @react-spectrum/s2, @adobe/spectrum-tokens, and
+    @internationalized/{date,number,string} (runtime / peer dependencies).
+  - A vendored copy of the React Spectrum S2 documentation site under
+    apps/comparison/vendor/s2-docs/, used as a comparison reference. That
+    directory carries its own upstream NOTICE at
+    apps/comparison/vendor/s2-docs/NOTICE.
+
+================================================================================
+MIT-derived work (Microsoft Tabster)
+================================================================================
+
+@proyecto-viviana/solidaria includes a SolidJS port of ShadowTreeWalker. Adobe's
+source is a modified portion of Microsoft Tabster.
+
+Sources:
+  - Adobe React Aria:
+    https://github.com/adobe/react-spectrum/blob/5ecb3333001313e83898cd07644227897e3bae1f/packages/react-aria/src/utils/shadowdom/ShadowTreeWalker.ts
+  - Microsoft Tabster:
+    https://github.com/microsoft/tabster/blob/a89fc5d7e332d48f68d03b1ca6e344489d1c3898/src/Shadowdomize/ShadowTreeWalker.ts
+
+MIT License
+
+Copyright (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+The upstream React Spectrum NOTICE lists third-party sources that Adobe used or
+modified. It is available from the React Spectrum repository at
+https://github.com/adobe/react-spectrum/blob/main/NOTICE.txt and, for the
+vendored documentation site, at apps/comparison/vendor/s2-docs/NOTICE.
+The source-mapping audit determines which upstream notices apply to each part
+of this derivative work. This reference does not claim that the audit is
+complete.

package/README.md

@@ -1,22 +1,28 @@
 # @proyecto-viviana/ui
 
-Viviana UI's design-system package, built on Solid.
+Styled, accessible components for Solid 2: the Viviana design system.
 
-It builds on `@proyecto-viviana/solid-spectrum`, so Spectrum components are
-available from the root package and from deep component subpaths. It also ships
-Viviana components, tokens, and product patterns such as cards, chips,
-conversation, layout, logo, and timeline pieces.
+Buttons, text fields, pickers, menus, tabs, calendars, color controls, and list
+and tree views. The keyboard, screen-reader, and internationalization behavior
+is ported from Adobe's React Aria. The tokens and the type are Viviana's own.
 
-This package is part of Viviana UI, an unofficial open-source Solid port and
-design-system suite built from Adobe's React Stately, React Aria, React Aria
-Components, and React Spectrum S2. It is not affiliated with Adobe.
+This is the package to start with. Reach for a lower one only when you need to
+build behavior yourself.
 
 ## Install
 
+Requires **Solid 2**. `solid-js` and `@solidjs/web` are peer dependencies, at
+`>=2.0.0-rc.9 <3`.
+
 ```bash
-npm install @proyecto-viviana/ui solid-js
+npm install @proyecto-viviana/ui@rc solid-js@next @solidjs/web@next
 ```
 
+The release candidate is on the `rc` tag. The `latest` tag is the Solid 1
+line.
+
+## Example
+
 ```tsx
 import { Provider, Button } from "@proyecto-viviana/ui";
 import { TextField } from "@proyecto-viviana/ui/TextField";
@@ -33,45 +39,38 @@ export function App() {
 }
 ```
 
-Deep imports such as `@proyecto-viviana/ui/TextField` are preferred in app code.
-The root barrel is convenient for examples and shared entry points.
+Deep imports such as `@proyecto-viviana/ui/TextField` are preferred in app
+code. The root barrel is for examples and shared entry points.
 
 ## Styling
 
-Components do not inject CSS. Import the design-system CSS once at your app
-entry.
-
-Most apps need one import — `components.css` already contains the other three:
+Component styling ships as CSS, not as JavaScript. Import it once, at your app
+entry, before your own stylesheets.
 
-```ts
-import "@proyecto-viviana/ui/components.css";
-```
+| Subpath                   | Contents                                                         |
+| ------------------------- | ---------------------------------------------------------------- |
+| `components.css`          | `font-faces.css` + `theme.css` + `styles.css`. The usual import. |
+| `components-no-fonts.css` | `theme.css` + `styles.css`, without package font declarations.   |
+| `theme.css`               | The token layer alone: it imports `viviana-tokens.css`.          |
+| `styles.css`              | Generated component rules, without fonts or tokens.              |
+| `font-faces.css`          | The Geist register: Geist Pixel, Geist, Geist Mono.              |
+| `viviana-tokens.css`      | The tokens themselves, to theme against directly.                |
 
-Apps that manage font loading themselves can import the halves separately:
+To omit the package's font declarations, optionally replace the `components.css`
+import with:
 
 ```ts
-import "@proyecto-viviana/ui/theme.css";
-import "@proyecto-viviana/ui/styles.css";
+import "@proyecto-viviana/ui/components-no-fonts.css";
 ```
 
-| Subpath          | Contents                                                         |
-| ---------------- | ---------------------------------------------------------------- |
-| `components.css` | `font-faces.css` + `theme.css` + `styles.css`. The usual import. |
-| `theme.css`      | Color-scheme tokens + Viviana brand `--color-*` variables.       |
-| `styles.css`     | Generated component rules, without font faces or tokens.         |
-| `font-faces.css` | Font-face declarations, including the Geist register.            |
-
-Keep these as `@import` statements at the very top of your CSS entry, or as JS
-imports before any other stylesheet. `font-faces.css` begins with a remote
-`@import` for the Geist family, and CSS drops an `@import` that any rule
-precedes — load it after your own rules and the Geist register silently falls
+`font-faces.css` opens with a remote `@import`, and CSS drops an `@import` that
+any rule precedes. Load it after your own rules and the fonts silently fall
 back to the default sans-serif.
 
-### Using Tailwind alongside these styles
+### Alongside Tailwind
 
-The library ships no Tailwind and requires none. If your app uses Tailwind, the
-two coexist — but only if you declare the cascade layer order yourself, **before
-any import**:
+This package ships no Tailwind and needs none. To use both, declare the layer
+order yourself, before any import:
 
 ```css
 @layer theme, base, _, L, components, utilities;
@@ -80,61 +79,133 @@ any import**:
 @import "@proyecto-viviana/ui/components.css";
 ```
 
-`_` and `L` are the layers our generated component rules live in. Layer order is
-otherwise decided by first appearance, and both possible accidents are silent:
+`_` and `L` are the two layers the generated component rules live in. Layer
+order is otherwise decided by first appearance, and both accidents are silent:
+declare nothing and our layers sort last, so a `bg-red-500` on one of our
+components does nothing; put our layers first and Tailwind's Preflight strips
+our components back to bare.
 
-- **No declaration.** Tailwind's sheet is seen first, so our layers sort last and
-  win. A `bg-red-500` on one of our components does nothing at all — the class is
-  in the DOM, the color never applies.
-- **Our layers first.** Tailwind's Preflight (`@layer base`) then outranks us, and
-  its `button { background-color: transparent }` strips our components back to
-  bare.
+## Server rendering
 
-The order above is the only one that gets both halves right: Preflight cannot
-reach our components, and Tailwind utilities still override them.
+The package ships compiled DOM output for a plain `import`, and preserved JSX
+under the `solid` export condition, which your bundler compiles for the server.
+A server that loads the DOM build cannot render it. With Vite, keep the family
+inside the bundle:
 
-## Authoring `style()`
+```ts
+import { defineConfig } from "vite";
+import solid from "@solidjs/vite-plugin";
+
+const packages = [
+  "@proyecto-viviana/ui",
+  "@proyecto-viviana/solid-spectrum",
+  "@proyecto-viviana/solidaria-components",
+  "@proyecto-viviana/solidaria",
+  "@proyecto-viviana/solid-stately",
+];
+
+export default defineConfig({
+  plugins: [solid({ ssr: true })],
+  optimizeDeps: { exclude: packages },
+  ssr: { noExternal: [/@proyecto-viviana\/.*/] },
+});
+```
+
+`@solidjs/vite-plugin` is the Solid 2 plugin (this repository pins
+`3.0.0-next.44`); `vite-plugin-solid` targets Solid 1. The project's own docs
+site server-renders with the same `noExternal` line.
 
-Using the published components does not require a macro plugin. Their styles are
-already generated in the package build.
+## Authoring `style()`
 
-You only need the macro setup if your app writes its own `style()` calls from
-`@proyecto-viviana/ui/style`:
+Using the published components needs no macro plugin. Their styles are
+generated when the package is built. You need the macro only if your app
+writes its own `style()` calls:
 
 ```ts
 import { style } from "@proyecto-viviana/ui/style" with { type: "macro" };
 ```
 
-For Vite apps, use the package helper:
+For Vite, use the package helper:
 
 ```ts
 import { defineConfig } from "vite";
-import solid from "vite-plugin-solid";
+import solid from "@solidjs/vite-plugin";
 import { vivianaMacros } from "@proyecto-viviana/ui/vite";
 
+const packages = [
+  "@proyecto-viviana/ui",
+  "@proyecto-viviana/solid-spectrum",
+  "@proyecto-viviana/solidaria-components",
+  "@proyecto-viviana/solidaria",
+  "@proyecto-viviana/solid-stately",
+];
+
 export default defineConfig({
   plugins: [vivianaMacros(), solid({ ssr: true })],
-  optimizeDeps: {
-    exclude: ["@proyecto-viviana/ui", "@proyecto-viviana/solid-spectrum"],
-  },
-  ssr: {
-    noExternal: ["@proyecto-viviana/ui", "@proyecto-viviana/solid-spectrum"],
-  },
+  optimizeDeps: { exclude: packages },
+  ssr: { noExternal: [/@proyecto-viviana\/.*/] },
 });
 ```
 
-`vivianaMacros()` uses `unplugin-parcel-macros`, which is an optional peer. Add it
-as a dev dependency when you use the helper:
+`vivianaMacros()` uses `unplugin-parcel-macros`, an optional peer. Add it as a
+dev dependency when you use the helper:
 
 ```bash
 npm install -D unplugin-parcel-macros
 ```
 
+## In the chain
+
+```text
+solid-stately
+      ↓
+solidaria
+      ↓
+solidaria-components
+      ↓
+      ├─ solid-spectrum
+      ├─ @proyecto-viviana/ui    ← you are here
+      ├─ kumo
+      └─ geist
+```
+
+It depends on the three headless packages. It does not depend on
+`@proyecto-viviana/solid-spectrum` at run time; the two are siblings over the
+same foundation.
+
 ## Status
 
-`@proyecto-viviana/ui` is published and in active development. Expect APIs,
-package boundaries, and component behavior to keep tightening while the suite
-settles.
+Published, and changing. APIs, package boundaries, and component behavior
+are still tightening. An export is a floor, not proof that a component matches
+upstream.
 
 The package ships ESM, preserved-JSX `solid` exports, and TypeScript
-declarations.
+declarations. `sideEffects` lists only `*.css`, so a bundler tree-shakes the
+JavaScript and keeps your stylesheet imports.
+
+What this release candidate is known to get wrong is listed under
+[known gaps](https://github.com/proyecto-viviana/ui#known-gaps-in-this-release-candidate).
+
+## Evidence
+
+```bash
+vp run --filter @proyecto-viviana/ui build
+vp run test:run
+```
+
+The docs site's accessibility run, `vp run a11y:check`, is not green in this
+candidate and carries exemption lists; it is not evidence for this package.
+
+What "ported" means here, and what evidence a component carries before it
+counts, is [the evidence bar](https://github.com/proyecto-viviana/ui/blob/main/.claude/current/certification.md).
+
+## Links
+
+- Documentation: <https://ui.proyectoviviana.org>
+- Repository: <https://github.com/proyecto-viviana/ui>
+
+## License
+
+MIT AND Apache-2.0. Our work is MIT; the part derived from Adobe's React
+Spectrum S2 keeps Apache-2.0. Both licenses and the project `NOTICE` ship in
+this package.

package/dist/Accordion.d.ts

@@ -0,0 +1,2 @@
+export * from "./accordion";
+//# sourceMappingURL=Accordion.d.ts.map

package/dist/Accordion.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Accordion.d.ts","sourceRoot":"","sources":["../src/Accordion.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC"}

package/dist/Accordion.js

@@ -0,0 +1,3 @@
+import { Disclosure, DisclosureContext, DisclosureHeader, DisclosurePanel, DisclosureTitle } from "./disclosure/index.js";
+import { Accordion, AccordionContext, AccordionHeader, AccordionItem, AccordionItemHeader, AccordionItemPanel, AccordionItemTitle, AccordionPanel, AccordionTitle } from "./accordion/index.js";
+export { Accordion, AccordionContext, AccordionHeader, AccordionItem, AccordionItemHeader, AccordionItemPanel, AccordionItemTitle, AccordionPanel, AccordionTitle, Disclosure, DisclosureContext, DisclosureHeader, DisclosurePanel, DisclosureTitle };

package/dist/Accordion.jsx

@@ -0,0 +1,3 @@
+import { Disclosure, DisclosureContext, DisclosureHeader, DisclosurePanel, DisclosureTitle } from "./disclosure/index.jsx";
+import { Accordion, AccordionContext, AccordionHeader, AccordionItem, AccordionItemHeader, AccordionItemPanel, AccordionItemTitle, AccordionPanel, AccordionTitle } from "./accordion/index.jsx";
+export { Accordion, AccordionContext, AccordionHeader, AccordionItem, AccordionItemHeader, AccordionItemPanel, AccordionItemTitle, AccordionPanel, AccordionTitle, Disclosure, DisclosureContext, DisclosureHeader, DisclosurePanel, DisclosureTitle };

package/dist/ActionBar.d.ts

@@ -0,0 +1,2 @@
+export * from "./actionbar";
+//# sourceMappingURL=ActionBar.d.ts.map

package/dist/ActionBar.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ActionBar.d.ts","sourceRoot":"","sources":["../src/ActionBar.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC"}

package/dist/ActionBar.js

@@ -0,0 +1,2 @@
+import { ActionBar, ActionBarContainer, ActionBarContext, createActionBarContainer } from "./actionbar/index.js";
+export { ActionBar, ActionBarContainer, ActionBarContext, createActionBarContainer };

package/dist/ActionBar.jsx

@@ -0,0 +1,2 @@
+import { ActionBar, ActionBarContainer, ActionBarContext, createActionBarContainer } from "./actionbar/index.jsx";
+export { ActionBar, ActionBarContainer, ActionBarContext, createActionBarContainer };

package/dist/ActionButtonGroup.d.ts

@@ -0,0 +1,2 @@
+export * from "./actionbuttongroup";
+//# sourceMappingURL=ActionButtonGroup.d.ts.map

package/dist/ActionButtonGroup.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ActionButtonGroup.d.ts","sourceRoot":"","sources":["../src/ActionButtonGroup.ts"],"names":[],"mappings":"AAAA,cAAc,qBAAqB,CAAC"}

package/dist/ActionButtonGroup.js

@@ -0,0 +1,2 @@
+import { ActionButtonGroup } from "./actionbuttongroup/index.js";
+export { ActionButtonGroup };

package/dist/ActionButtonGroup.jsx

@@ -0,0 +1,2 @@
+import { ActionButtonGroup } from "./actionbuttongroup/index.jsx";
+export { ActionButtonGroup };

package/dist/ActionGroup.d.ts

@@ -0,0 +1,2 @@
+export * from "./actiongroup";
+//# sourceMappingURL=ActionGroup.d.ts.map

package/dist/ActionGroup.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ActionGroup.d.ts","sourceRoot":"","sources":["../src/ActionGroup.ts"],"names":[],"mappings":"AAAA,cAAc,eAAe,CAAC"}

package/dist/ActionGroup.js

@@ -0,0 +1,2 @@
+import { ActionGroup } from "./actiongroup/index.js";
+export { ActionGroup };

package/dist/ActionGroup.jsx

@@ -0,0 +1,2 @@
+import { ActionGroup } from "./actiongroup/index.jsx";
+export { ActionGroup };

package/dist/ActionMenu.js

@@ -1,5 +1,6 @@
-import { a as Header, d as Heading, l as Keyboard, s as Text } from "./_chunk/text.js";
-import { n as ActionMenuContext, t as ActionMenu } from "./_chunk/ActionMenu.js";
+import { t as Keyboard } from "./_chunk/Keyboard.js";
+import { a as Header, l as Heading, s as Text } from "./_chunk/text.js";
 import { d as UnavailableMenuItemTrigger, l as MenuTrigger, o as MenuItem, p as SubmenuTrigger, s as MenuSection, t as Collection } from "./_chunk/menu.js";
-import { r as ContextualHelpPopover } from "./_chunk/contextualhelp.js";
+import { ContextualHelpPopover } from "./contextualhelp/index.js";
+import { ActionMenu, ActionMenuContext } from "./menu/ActionMenu.js";
 export { ActionMenu, ActionMenuContext, Collection, ContextualHelpPopover, Header, Heading, Keyboard, MenuItem, MenuSection, MenuTrigger, SubmenuTrigger, Text, UnavailableMenuItemTrigger };

package/dist/ActionMenu.jsx

@@ -1,5 +1,6 @@
-import { a as Header, d as Heading, l as Keyboard, s as Text } from "./_chunk/text.jsx";
-import { n as ActionMenuContext, t as ActionMenu } from "./_chunk/ActionMenu.jsx";
+import { t as Keyboard } from "./_chunk/Keyboard.jsx";
+import { a as Header, l as Heading, s as Text } from "./_chunk/text.jsx";
 import { d as UnavailableMenuItemTrigger, l as MenuTrigger, o as MenuItem, p as SubmenuTrigger, s as MenuSection, t as Collection } from "./_chunk/menu.jsx";
-import { r as ContextualHelpPopover } from "./_chunk/contextualhelp.jsx";
+import { ContextualHelpPopover } from "./contextualhelp/index.jsx";
+import { ActionMenu, ActionMenuContext } from "./menu/ActionMenu.jsx";
 export { ActionMenu, ActionMenuContext, Collection, ContextualHelpPopover, Header, Heading, Keyboard, MenuItem, MenuSection, MenuTrigger, SubmenuTrigger, Text, UnavailableMenuItemTrigger };