@commercetools/nimbus 0.0.1 → 0.0.3

package/package.json

@@ -1,11 +1,39 @@
 {
   "name": "@commercetools/nimbus",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "main": "./dist/index.umd.cjs",
   "module": "./dist/index.js",
   "type": "module",
   "types": "./dist/index.d.ts",
-  "sideEffects": false,
+  "exports": {
+    ".": {
+      "import": {
+        "types": "./dist/index.d.ts",
+        "default": "./dist/index.js"
+      },
+      "require": {
+        "types": "./dist/index.d.ts",
+        "default": "./dist/index.umd.cjs"
+      }
+    }
+  },
+  "files": [
+    "dist"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "sideEffects": [
+    "*.css"
+  ],
+  "source": "src/index.ts",
+  "typesVersions": {
+    "*": {
+      "*": [
+        "./dist/index.d.ts"
+      ]
+    }
+  },
   "devDependencies": {
     "@chakra-ui/cli": "catalog:react",
     "@pandacss/types": "catalog:react",
@@ -20,7 +48,6 @@
     "@testing-library/user-event": "catalog:tooling",
     "@types/react": "catalog:react",
     "@types/react-dom": "catalog:react",
-    "@types/testing-library__dom": "^7.5.0",
     "@vitejs/plugin-react": "catalog:tooling",
     "@vitest/browser": "catalog:tooling",
     "@vitest/coverage-v8": "catalog:tooling",
@@ -46,10 +73,10 @@
     "@emotion/is-prop-valid": "catalog:react",
     "@react-aria/optimize-locales-plugin": "^1.1.4",
     "next-themes": "catalog:react",
-    "react-aria": "^3.37.0",
-    "react-aria-components": "1.6.0",
+    "react-aria": "catalog:react",
+    "react-aria-components": "catalog:react",
     "react-hotkeys-hook": "^4.6.1",
-    "react-stately": "^3.35.0",
+    "react-stately": "catalog:react",
     "react-use": "^17.5.1"
   },
   "scripts": {

package/.storybook/apca-check/index.ts

@@ -1,150 +0,0 @@
-import axe, { type Check, Rule } from "axe-core";
-import { calcAPCA } from "apca-w3";
-
-type ConformanceLevel = "custom";
-
-type ConformanceThresholdFn = (
-  fontSize: string,
-  fontWeight: string
-) => number | null;
-
-// Augment Axe types to include the color utilities we use in this file
-// https://github.com/dequelabs/axe-core/blob/develop/lib/commons/color/color.js
-type Color = {
-  red: number;
-  green: number;
-  blue: number;
-  alpha: number;
-  toHexString: () => string;
-};
-declare module "axe-core" {
-  interface Commons {
-    color: {
-      getForegroundColor: (
-        node: HTMLElement,
-        _: unknown,
-        bgColor: Color | null
-      ) => Color | null;
-      getBackgroundColor: (node: HTMLElement) => Color | null;
-    };
-  }
-}
-
-const generateColorContrastAPCAConformanceCheck = (
-  conformanceLevel: string,
-  conformanceThresholdFn: ConformanceThresholdFn
-): Check => ({
-  id: `color-contrast-apca-${conformanceLevel}-conformance`,
-  metadata: {
-    impact: "serious",
-    messages: {
-      pass:
-        "Element has sufficient APCA " +
-        conformanceLevel +
-        " level lightness contrast (Lc) of ${data.apcaContrast}Lc (foreground color: ${data.fgColor}, background color: ${data.bgColor}, font size: ${data.fontSize}, font weight: ${data.fontWeight}). Expected minimum APCA contrast of ${data.apcaThreshold}}",
-      fail: {
-        default:
-          "Element has insufficient APCA " +
-          conformanceLevel +
-          " level contrast of ${data.apcaContrast}Lc (foreground color: ${data.fgColor}, background color: ${data.bgColor}, font size: ${data.fontSize}, font weight: ${data.fontWeight}). Expected minimum APCA lightness contrast of ${data.apcaThreshold}Lc",
-        increaseFont:
-          "Element has insufficient APCA " +
-          conformanceLevel +
-          " level contrast of ${data.apcaContrast}Lc (foreground color: ${data.fgColor}, background color: ${data.bgColor}, font size: ${data.fontSize}, font weight: ${data.fontWeight}). Increase font size and/or font weight to meet APCA conformance minimums",
-        placeholder:
-          "Element has insufficient APCA " +
-          conformanceLevel +
-          " level contrast of ${data.apcaContrast}Lc (foreground color: ${data.fgColor}, background color: ${data.bgColor}, font size: ${data.fontSize}, font weight: ${data.fontWeight}). Using reduced threshold of 30Lc for placeholder",
-      },
-      incomplete: "Unable to determine APCA lightness contrast (Lc)",
-    },
-  },
-  evaluate(n) {
-    const node = n as HTMLElement;
-    const nodeStyle = window.getComputedStyle(node);
-    const fontSize = nodeStyle.getPropertyValue("font-size");
-    const fontWeight = nodeStyle.getPropertyValue("font-weight");
-
-    const bgColor: Color | null = axe.commons.color.getBackgroundColor(node);
-    const fgColor: Color | null = axe.commons.color.getForegroundColor(
-      node,
-      false,
-      bgColor
-    );
-
-    // missing data to determine APCA contrast for this node
-    if (!bgColor || !fgColor || !fontSize || !fontWeight) {
-      return undefined;
-    }
-
-    const toRGBA = (color: Color) => {
-      return `rgba(${color.red}, ${color.green}, ${color.blue}, ${color.alpha})`;
-    };
-
-    const apcaContrast = Math.abs(
-      calcAPCA(toRGBA(fgColor), toRGBA(bgColor)) as number
-    );
-
-    // Check if element has data-placeholder attribute
-    const hasPlaceholderAttr = node.hasAttribute("data-placeholder");
-    const originalThreshold = conformanceThresholdFn(fontSize, fontWeight);
-
-    // Use reduced threshold of 30 for placeholders, otherwise use original threshold
-    const apcaThreshold = hasPlaceholderAttr ? 30 : originalThreshold;
-
-    this.data({
-      fgColor: fgColor.toHexString(),
-      bgColor: bgColor.toHexString(),
-      fontSize: `${((parseFloat(fontSize) * 72) / 96).toFixed(
-        1
-      )}pt (${parseFloat(fontSize)}px)`,
-      fontWeight: fontWeight,
-      apcaContrast: Math.round(apcaContrast * 100) / 100,
-      apcaThreshold: apcaThreshold,
-      messageKey:
-        apcaThreshold === null
-          ? "increaseFont"
-          : hasPlaceholderAttr
-            ? "placeholder"
-            : "default",
-    });
-
-    return apcaThreshold ? apcaContrast >= apcaThreshold : false;
-  },
-});
-
-const generateColorContrastAPCARule = (conformanceLevel: string): Rule => ({
-  id: `color-contrast-apca-${conformanceLevel}`,
-  impact: "serious",
-  matches: "color-contrast-matches",
-  metadata: {
-    description: `Ensures the contrast between foreground and background colors meets APCA ${conformanceLevel} level conformance minimums thresholds`,
-    help: "Elements must meet APCA conformance minimums thresholds",
-    helpUrl:
-      "https://readtech.org/ARC/tests/visual-readability-contrast/?tn=criterion",
-  },
-  all: [`color-contrast-apca-${conformanceLevel}-conformance`],
-  tags: ["apca", "wcag3", `apca-${conformanceLevel}`],
-});
-
-const registerAPCACheck = (
-  conformanceLevel: ConformanceLevel,
-  conformanceThresholdFn: ConformanceThresholdFn
-) => {
-  if (typeof conformanceThresholdFn !== "function") {
-    throw new Error("Conformance threshold function is required");
-  }
-
-  return {
-    rules: [generateColorContrastAPCARule(conformanceLevel)],
-    checks: [
-      generateColorContrastAPCAConformanceCheck(
-        conformanceLevel,
-        conformanceThresholdFn
-      ),
-    ],
-  };
-};
-
-export type { ConformanceLevel, ConformanceThresholdFn };
-export default registerAPCACheck;

package/.storybook/main.ts

@@ -1,64 +0,0 @@
-import type { StorybookConfig } from "@storybook/react-vite";
-
-import { join, dirname } from "path";
-
-/**
- * This function is used to resolve the absolute path of a package.
- * It is needed in projects that use Yarn PnP or are set up within a monorepo.
- */
-function getAbsolutePackagePath(value: string): any {
-  return dirname(require.resolve(join(value, "package.json")));
-}
-
-const config: StorybookConfig = {
-  stories: ["../src/**/*.stories.tsx"],
-  addons: [
-    getAbsolutePackagePath("@storybook/addon-essentials"),
-    getAbsolutePackagePath("@storybook/addon-a11y"),
-    getAbsolutePackagePath("storybook-dark-mode"),
-    getAbsolutePackagePath("@storybook/experimental-addon-test"),
-  ],
-  framework: {
-    name: getAbsolutePackagePath("@storybook/react-vite"),
-    options: {},
-  },
-  refs: {
-    "@chakra-ui/react": {
-      disable: true,
-    },
-  },
-  core: {
-    disableTelemetry: true,
-  },
-  typescript: {
-    reactDocgen: "react-docgen-typescript",
-    // Provide your own options if necessary.
-    // See https://storybook.js.org/docs/configure/typescript for more information.
-    reactDocgenTypescriptOptions: {
-      compilerOptions: {
-        allowSyntheticDefaultImports: false,
-        esModuleInterop: false,
-      },
-
-      // Extend if needed...
-      propFilter: (prop) => {
-        // ... common props that every component may have
-        const whitelistedProps = ["ref", "colorScheme", "asChild"];
-
-        // ... props coming from the nimbus package
-        const isOneOfOurTypes = !!prop.parent?.fileName.includes("nimbus/src");
-
-        // ... props coming from the react-aria package
-        const isReactAriaProp =
-          !!prop.parent?.fileName.includes("@react-types");
-
-        return (
-          isOneOfOurTypes ||
-          isReactAriaProp ||
-          whitelistedProps.includes(prop.name)
-        );
-      },
-    },
-  },
-};
-export default config;

package/.storybook/preview.tsx

@@ -1,92 +0,0 @@
-import React, { useEffect, useState } from "react";
-import type { Preview } from "@storybook/react";
-import { NimbusProvider } from "../src";
-import { DARK_MODE_EVENT_NAME } from "storybook-dark-mode";
-import { addons } from "@storybook/preview-api";
-
-import APCACheck from "./apca-check";
-
-const apca = APCACheck("custom", (fontSize: string) => {
-  const size = parseFloat(fontSize);
-  switch (true) {
-    case size >= 32:
-      return 45;
-    default:
-      return 60;
-  }
-});
-
-// get channel to listen to event emitter
-const channel = addons.getChannel();
-
-const ThemeDecorator = ({ children }) => {
-  const [isDark, setDark] = useState(false);
-  const theme = isDark ? "dark" : "light";
-
-  useEffect(() => {
-    const { current } = JSON.parse(
-      // TODO: find out if there is a more elegant solution
-      localStorage.getItem("sb-addon-themes-3") || "{}"
-    );
-
-    setDark(current === "dark");
-
-    channel.on(DARK_MODE_EVENT_NAME, (darkMode) => {
-      setDark(darkMode);
-    });
-
-    return () => channel.off(DARK_MODE_EVENT_NAME, setDark);
-  }, [channel]);
-
-  useEffect(() => {
-    document.documentElement.classList.remove("light", "dark");
-    document.documentElement.classList.add(theme);
-  }, [theme]);
-
-  return <NimbusProvider defaultTheme={theme}>{children}</NimbusProvider>;
-};
-
-const preview: Preview = {
-  parameters: {
-    darkMode: {
-      stylePreview: true,
-      classTarget: "html",
-    },
-    backgrounds: {
-      disable: true,
-    },
-    a11y: {
-      config: {
-        checks: [...apca.checks],
-        rules: [
-          {
-            // disabled, as radix is using APCA algorithm while Storybook uses WCAG
-            // @see https://web.dev/articles/color-and-contrast-accessibility#apca)
-
-            id: "color-contrast",
-            enabled: false,
-          },
-          ...apca.rules,
-        ],
-      },
-      /*
-       * Axe's options parameter
-       * See https://github.com/dequelabs/axe-core/blob/develop/doc/API.md#options-parameter
-       * to learn more about the available options.
-       */
-      options: {},
-    },
-  },
-  tags: ["autodocs", "a11y-test"],
-  decorators: [
-    (Story) => {
-      return (
-        <ThemeDecorator>
-          <Story />
-        </ThemeDecorator>
-      );
-    },
-  ],
-};
-
-export default preview;

package/.storybook/vitest.setup.ts

@@ -1,13 +0,0 @@
-import * as a11yAddonAnnotations from "@storybook/addon-a11y/preview";
-import { beforeAll } from "vitest";
-import { setProjectAnnotations } from "@storybook/react";
-import * as projectAnnotations from "./preview";
-
-// This is an important step to apply the right configuration when testing your stories.
-// More info at: https://storybook.js.org/docs/api/portable-stories/portable-stories-vitest#setprojectannotations
-const project = setProjectAnnotations([
-  a11yAddonAnnotations,
-  projectAnnotations,
-]);
-
-beforeAll(project.beforeAll);

package/docs/architecture-decisions/adr-0001-consumer-component-apis.md

@@ -1,177 +0,0 @@
-# ADR: On Consumer Component API's
-
-## Context
-
-We needed an Alert component to show informational or warning messages. The
-component should allow:
-
-- A title and description.
-- An optional dismiss button.
-- Additional buttons or controls.
-- Spacing/styling overrides (e.g. px, py).
-
-In early explorations, we tried to expose everything via props on the main
-`Alert`—this seemed convenient but would quickly became unwieldy when
-requirements changed. This led to a discussion about how to structure the API
-for components in a way that is both flexible and maintainable.
-
-## Early Attempts
-
-### Attempt A: One Big Alert with Child Buttons
-
-```jsx
-<Alert
-  title="title"
-  description="description"
-  onDismiss={() => void}
-  px="4"
-  py="2"
->
-  <button>Dismiss</button>
-  <button>Click me</button>
-</Alert>
-```
-
-1. title and description are top-level props.
-2. children are the alert's buttons.
-
-**Issue**: If we need new kinds of controls (e.g., a link, extra text, or
-re-positioned buttons), we must keep adding or repurposing props. The line
-between "belongs in children" vs. "belongs in dedicated props" can become
-blurry.
-
-### Attempt B: Specialized Props for Each Slot
-
-```jsx
-<Alert
-  alertTitleStyle="bold"
-  title="title"
-  description="description"
-  onDismiss={() => void}
-  px="4"
-  py="2"
-  alertControls={
-    <>
-      <button>Dismiss</button>
-      <button>Click me</button>
-    </>
-  }
-/>
-```
-
-1. We introduced an alertControls prop for the buttons.
-2. We also added alertTitleStyle to control how the title looks.
-
-**Issue**: As the design evolves (e.g., "Now we need the title right‐aligned, or
-a sub‐title below the main title"), we keep adding ad-hoc props like
-titlePosition, alertControlsAlignment, etc. The `<Alert>` props list grows large
-and messy.
-
-### Attempt C: Even More Props for Layout / Positioning
-
-```jsx
-<Alert
-  alertTitleStyle="bold"
-  title="title"
-  titlePosition="right"
-  description="description"
-  onDismiss={() => void}
-  px="4"
-  py="2"
-  alertControls={
-    <>
-      <button>Dismiss</button>
-      <button>Click me</button>
-    </>
-  }
-/>
-```
-
-**Issue**: The top-level `<Alert>` component now has numerous styling, layout,
-and content props all jumbled together. If a new design wants a second dismiss
-button or a multi-line description, we must add more props. This is non-scalable
-and not very semantic.
-
-## Final Decision: Compound Components
-
-We decided to adopt compound components (a pattern in which sub-elements are
-also React components). The final API looks like:
-
-```jsx
-<Alert px="4" py="2">
-  <Alert.Title fontStyle="bold">
-    Alert Title
-  </Alert.Title>
-  <Alert.Description>
-    A short alert description.
-  </Alert.Description>
-  <Alert.DismissButton onClick={() => void} />
-</Alert>
-```
-
-### Key Changes:
-
-1. Children become semantic slots: `<Alert.Title>`, `<Alert.Description>`, and
-   `<Alert.DismissButton>`.
-2. Each slot can handle its own styling or props. For instance, Alert.Title
-   might accept a fontStyle prop, Alert.DismissButton handles its own click
-   event.
-3. The root `<Alert>` only handles general layout or high-level variant props
-   (e.g., px, py, severity).
-
-### Why this is better:
-
-- **Clear separation of concerns**: Layout/styling for each slot belongs to that
-  slot. The main `<Alert>` only handles spacing or theming.
-- **Easier to extend**: If we need a second sub-element (e.g., `<Alert.Icon>` or
-  `<Alert.Footer>`), we just introduce a new subcomponent. We don't clog
-  `<Alert>` with more props.
-- **Semantic**: `<Alert.Title>` and `<Alert.Description>` are more descriptive
-  than `title="..."` or `alertControls={...}`.
-
-## Consequences
-
-- We have a more verbose but much more flexible API.
-- Consumers build their alert in a semantic, composable way.
-- We can add or rearrange subcomponents without rewriting the main `<Alert>`
-  props or code.
-- If developers want quick usage (like a single short message), they might find
-  passing a couple props simpler – but we've prioritized long-term
-  maintainability and clarity.
-
-## Examples in Practice
-
-### 1. Basic Alert
-
-```jsx
-<Alert>
-  <Alert.Title>Warning!</Alert.Title>
-  <Alert.Description>Please fill out all required fields.</Alert.Description>
-  <Alert.DismissButton onClick={onClose} />
-</Alert>
-```
-
-### 2. Alert with Extra Controls
-
-```jsx
-<Alert px="4" py="3">
-  <Alert.Title fontStyle="bold">Network Error</Alert.Title>
-  <Alert.Description>
-    We could not reach the server. Please try again.
-  </Alert.Description>
-  <Alert.DismissButton onClick={onClose} />
-  <Alert.Controls>
-    <Button onClick={onRetry}>Retry</Button>
-  </Alert.Controls>
-</Alert>
-```
-
-## Summary
-
-- Inline props for major sections quickly lead to "prop creep."
-- Compound components keep `<Alert>` minimal and delegate content/markup details
-  to semantically named subcomponents.
-- Layout changes or extra features do not require new top-level props on
-  `<Alert>`.
-
-This approach scales better and is more maintainable as the design evolves.

package/docs/architecture-decisions/adr-0002-compound-component-extraction.md

@@ -1,82 +0,0 @@
-# ADR: Standardizing Compound Component Extraction to a `components` Directory
-
-## Context
-
-To enhance the organization, maintainability, and scalability of our components
-that utilize the compound component pattern, we are establishing a consistent
-directory structure for their implementation. This ADR outlines the principle of
-extracting the core root component and its associated compound sub-components
-into a dedicated `components` subdirectory.
-
-## Decision
-
-For any component (`<ComponentName>`) that follows the compound component
-pattern (where sub-components like `<ComponentName.Part>`,
-`<ComponentName.Control>`, etc., are defined as properties of the main
-component), we will adopt the following directory structure:
-
-- The main component's directory will be
-  `packages/nimbus/src/components/<component-name>/`.
-- A subdirectory named `components` will be created within the main component's
-  directory: `packages/nimbus/src/components/<component-name>/components/`.
-- The implementation files for the root component (`<ComponentName.Root>`) and
-  all its compound sub-components (`<ComponentName.Part>`,
-  `<ComponentName.Control>`, etc.) will reside within this `components`
-  subdirectory.
-- The main `<component-name>.tsx` file within the `<component-name>` directory
-  will be responsible for:
-  - Importing the root component and all sub-components from the `components`
-    subdirectory.
-  - Re-exporting them as properties of the main `ComponentName` object.
-
-Storybook files (`<component-name>.stories.tsx`) will be updated to reflect this
-structure, primarily by referencing the appropriate root component (e.g.,
-`ComponentName.Root` or `ComponentName`) in the `Meta` configuration.
-
-## Why this is better:
-
-- **Consistent Code Organization:** This standardized structure will make it
-  easier for developers to locate the implementation files for any component
-  utilizing the compound pattern.
-- **Improved Maintainability:** Isolating the implementation of each part of a
-  compound component within its own file reduces the complexity of individual
-  files and minimizes the risk of unintended side effects during modifications.
-- **Enhanced Scalability:** As components grow and incorporate more
-  sub-components, this structure provides a clear and manageable way to organize
-  the increasing number of files.
-- **Clear Separation of Concerns:** Each file within the `components` directory
-  will focus on the implementation details of a specific part of the compound
-  component.
-
-## Consequences
-
-- **New Directory Structure:** Developers will need to be aware of this new
-  directory structure for all future and refactored compound components.
-- **Import Path Updates:** When working directly with the individual root or
-  sub-component implementations, import paths will need to reflect their
-  location within the `components` subdirectory. However, the main `index.tsx`
-  re-export should abstract this for most consumers using the compound component
-  API.
-- **Storybook Updates:** The `Meta` configuration in Storybook files for
-  compound components will need to point to the appropriate root component.
-
-## Examples
-
-**With `components` Subdirectory:**
-
-```
-packages/nimbus/src/components/component-name/index.tsx
-packages/nimbus/src/components/component-name/component-name.tsx
-packages/nimbus/src/components/component-name/components/component-name.root.tsx
-packages/nimbus/src/components/component-name/components/component-name.part.tsx
-packages/nimbus/src/components/component-name/components/component-name.control.tsx
-packages/nimbus/src/components/component-name/component-name.stories.tsx
-```
-
-## Summary
-
-Adopting this standardized directory structure for compound components will lead
-to a more organized, maintainable, and scalable UI Kit. By consistently
-separating the implementation details of the root and sub-components into a
-dedicated `components` subdirectory, we establish a clear pattern for future
-development and refactoring efforts.

package/src/components/accordion/accordion-context.tsx

@@ -1,17 +0,0 @@
-import React, { createContext } from "react";
-import type { DisclosureGroupState } from "react-stately";
-
-// Define types for the item context
-export interface ItemContextType {
-  isExpanded: boolean;
-  triggerRef: React.RefObject<HTMLButtonElement>;
-  panelRef: React.RefObject<HTMLDivElement>;
-  buttonProps: React.ButtonHTMLAttributes<HTMLButtonElement>;
-  panelProps: React.ButtonHTMLAttributes<HTMLButtonElement>;
-  isFocusVisible: boolean;
-}
-
-// Create and export the contexts
-export const ItemContext = createContext<ItemContextType | null>(null);
-export const DisclosureGroupStateContext =
-  createContext<DisclosureGroupState | null>(null);