@ntbjs/react-components 2.0.14 → 3.0.0-rc.1

package/types/hooks/useOnClickOutside.d.ts

@@ -0,0 +1,31 @@
+import type { DomEventMap } from './useEventListner';
+import type { RefObject } from 'react';
+/**
+ * The event names this hook can watch for. Narrower than `DomEventName` on
+ * purpose — the parameter is called `mouseEvent`, and a non-pointer event name
+ * here would silently never fire the outside-click check.
+ */
+export type OutsideClickEventName = 'mousedown' | 'mouseup' | 'click';
+/**
+ * What the handler receives. DERIVED from `DomEventMap` rather than written as
+ * `MouseEvent`, so it follows lib.dom if a future TypeScript retypes any of
+ * these three names (`click` has already moved between `MouseEvent` and
+ * `PointerEvent` upstream).
+ */
+export type OutsideClickEvent = DomEventMap[OutsideClickEventName];
+/**
+ * Calls `handler` when the chosen pointer event happens anywhere outside `ref`'s
+ * element and its descendants.
+ *
+ * `ref` IS TYPED AS NULLABLE BECAUSE THE BODY READS `ref?.current`. That is not
+ * defensiveness copied from elsewhere — it is the existing runtime contract, so
+ * the type records it. Contrast `useElementSize`, whose body reads `ref.current`
+ * and whose `ref` is therefore required.
+ *
+ * @param ref        the "inside" element. A click on it or on any descendant is
+ *                   ignored
+ * @param handler    called with the originating event for outside clicks only
+ * @param mouseEvent which event to listen for; defaults to `'mousedown'` so the
+ *                   callback fires before a click can move focus
+ */
+export declare function useOnClickOutside<T extends Node = HTMLElement>(ref: RefObject<T | null> | null | undefined, handler: (event: OutsideClickEvent) => void, mouseEvent?: OutsideClickEventName): void;

package/types/hooks/useTooltipAutoShow.d.ts

@@ -0,0 +1,80 @@
+/**
+ * What `useTooltipAutoShow` returns. Spread straight onto a `Tooltip` by
+ * `TextArea` and `CompactTextInput`.
+ */
+export interface TooltipAutoShow {
+    /** Clears the forced-visible state. Wire to the trigger's `onMouseLeave`. */
+    toolTipOnMouseLeave: () => void;
+    /**
+     * The last non-empty content. Sticky on purpose, so the tooltip can animate
+     * out with its text intact instead of emptying mid-transition.
+     */
+    toolTipContent: string;
+    /** `true` while there is no content, which suppresses the tooltip entirely. */
+    toolTipDisabled: boolean;
+    /**
+     * `true` | `undefined` — NEVER `false`, AND THE `undefined` IS LOAD-BEARING.
+     * `Tooltip` treats `visible` as the switch between UNCONTROLLED and CONTROLLED
+     * mode: `undefined` leaves the tooltip under its own `trigger` prop
+     * (hover/focus), while any boolean — including `false` — hands control to us
+     * permanently and the tooltip stops responding to hover for the rest of its
+     * life. So this type is `true | undefined` rather than the `boolean` it looks
+     * like it wants to be. DO NOT "SIMPLIFY" IT: widening to `boolean` compiles
+     * fine and silently breaks every hover tooltip in `TextArea` and
+     * `CompactTextInput`.
+     *
+     * That rule was tippy's and is now the library's own: `useFloatingPopover`
+     * decides controlled-ness with `typeof open === 'boolean'`, so this contract
+     * survived the Floating UI migration unchanged and deliberately.
+     *
+     * ONE SEMANTIC DIFFERENCE, RECORDED BECAUSE IT IS REAL EVEN THOUGH THE
+     * OBSERVABLE OUTCOME IS THE SAME. Going from `true` back to `undefined` used
+     * to leave the tippy instance SHOWN — `@tippyjs/react` only issues an
+     * imperative `show()`/`hide()` while `visible !== undefined`, so dropping out
+     * of controlled mode issued nothing and the tooltip stayed up until the
+     * reference's own `mouseleave` hid it. `useFloatingPopover` instead resolves
+     * to its uncontrolled state, which is closed. Both end with the tooltip
+     * hidden, because the caller drives this from `onMouseLeave` and that same
+     * pointer exit is what used to hide it; the new path just does not depend on a
+     * second event arriving.
+     */
+    toolTipVisible: true | undefined;
+}
+/**
+ * Tracks a tooltip's content and automatically forces it to be visible when the
+ * content transitions from empty → non-empty, then defaults to trigger prop.
+ *
+ * ================== PLAN C8, DECIDED: THIS STAYS A SEPARATE HOOK ==================
+ *
+ * The plan asks whether `useFloatingPopover` should absorb this. It should not,
+ * and the premise of the question turned out to be wrong.
+ *
+ * 1. **It does not read tippy's imperative instance API.** The plan describes it
+ *    as doing so, but measured — `grep -i tippy` over this file — the only match
+ *    is prose. There is no `_tippy`, no instance handle, no `show()`/`hide()`,
+ *    and no tippy import. Whatever was true when the plan was written, the
+ *    TypeScript migration left a hook that is pure React: two refs, one
+ *    `useState`, one `useEffect`.
+ * 2. **What it depends on is a CONTRACT, not an implementation**, namely the
+ *    `undefined`-means-uncontrolled rule documented on `toolTipVisible`.
+ *    `useFloatingPopover` preserves that rule exactly, so this file needed no
+ *    behavioural change to survive the migration — and did not get one.
+ * 3. **Merging it would put the wrong responsibility in the wrong place.** This
+ *    is a content-change detector: it compares the previous `content` string with
+ *    the current one and force-shows on the empty → non-empty edge.
+ *    `useFloatingPopover` owns position and interaction and never reads `content`
+ *    at all. Absorbing this would mean giving the positioning hook a `content`
+ *    parameter and a sticky-previous-value state machine for the benefit of the
+ *    two call sites that want it, out of the five it is meant to serve — three of
+ *    which (`SummaryCard`, `AssetAction`, `AssetGalleryCompactCard`) have no
+ *    content prop to diff.
+ *
+ * So the change here is documentation only: the JSDoc used to attribute the
+ * controlled-mode rule to tippy, and tippy is going away.
+ *
+ * @param content the tooltip text. `string`, because both call sites declare
+ *                `descriptionToolTip: PropTypes.string` with a `''` default —
+ *                the sticky `displayContent` ref would not survive a `ReactNode`
+ */
+declare function useTooltipAutoShow(content?: string): TooltipAutoShow;
+export default useTooltipAutoShow;

package/types/icons/index.d.ts

@@ -0,0 +1,41 @@
+import { ReactComponent as AddIcon } from './add.svg';
+import { ReactComponent as AddCircleIcon } from './add-circle.svg';
+import { ReactComponent as AlbumIcon } from './album.svg';
+import { ReactComponent as ArrowBackIcon } from './arrow-back.svg';
+import { ReactComponent as ArrowDropDownIcon } from './arrow-drop-down.svg';
+import { ReactComponent as ArrowForwardIcon } from './arrow-forward.svg';
+import { ReactComponent as AudioIcon } from './audio.svg';
+import { ReactComponent as BellIcon } from './bell.svg';
+import { ReactComponent as CheckCircleIcon } from './check-circle-filled.svg';
+import { ReactComponent as CheckRectangleIcon } from './check-rectangle-filled.svg';
+import { ReactComponent as CloseIcon } from './close.svg';
+import { ReactComponent as CorporateIcon } from './corporate.svg';
+import { ReactComponent as DeleteContextMenuIcon } from './delete-context-menu.svg';
+import { ReactComponent as DeleteIcon } from './delete.svg';
+import { ReactComponent as DesignServicesIcon } from './design-services.svg';
+import { ReactComponent as DownloadIcon } from './download.svg';
+import { ReactComponent as EditNoteIcon } from './edit-note.svg';
+import { ReactComponent as EditIcon } from './edit.svg';
+import { ReactComponent as ExpandMoreIcon } from './expand-more.svg';
+import { ReactComponent as FileIcon } from './file.svg';
+import { ReactComponent as FtpIcon } from './ftp.svg';
+import { ReactComponent as GearIcon } from './gear.svg';
+import { ReactComponent as HeadsetIcon } from './headset.svg';
+import { ReactComponent as LayersIcon } from './layers.svg';
+import { ReactComponent as LibraryAddIcon } from './library-add.svg';
+import { ReactComponent as LinkIcon } from './link.svg';
+import { ReactComponent as PdfIcon } from './pdf.svg';
+import { ReactComponent as PlayIcon } from './play.svg';
+import { ReactComponent as RemoveCircleIcon } from './remove-circle.svg';
+import { ReactComponent as SearchIcon } from './search.svg';
+import { ReactComponent as ShareIcon } from './share.svg';
+import { ReactComponent as ShoppingCartAddIcon } from './shopping_cart_add.svg';
+import { ReactComponent as StarFilledIcon } from './star-filled.svg';
+import { ReactComponent as StarIcon } from './star.svg';
+import { ReactComponent as TriangleRightIcon } from './triangle-right.svg';
+import { ReactComponent as VerificationIcon } from './verification.svg';
+import { ReactComponent as WarningCircleIcon } from './warning-circle.svg';
+import { ReactComponent as WarningTriangleIcon } from './warning-triangle.svg';
+import { ReactComponent as InfoRedIcon } from './info-red.svg';
+import { ReactComponent as InfoYellowIcon } from './info-yellow.svg';
+export { AddIcon, AddCircleIcon, AlbumIcon, ArrowBackIcon, ArrowDropDownIcon, ArrowForwardIcon, AudioIcon, BellIcon, CheckCircleIcon, CheckRectangleIcon, CloseIcon, CorporateIcon, DeleteContextMenuIcon, DeleteIcon, DesignServicesIcon, DownloadIcon, EditNoteIcon, EditIcon, ExpandMoreIcon, FileIcon, FtpIcon, GearIcon, HeadsetIcon, LayersIcon, LibraryAddIcon, LinkIcon, PdfIcon, PlayIcon, RemoveCircleIcon, SearchIcon, ShareIcon, ShoppingCartAddIcon, StarFilledIcon, StarIcon, TriangleRightIcon, VerificationIcon, WarningCircleIcon, WarningTriangleIcon, InfoRedIcon, InfoYellowIcon };

package/types/ssr/index.d.ts

@@ -0,0 +1 @@
+export { ServerStyleSheet } from "styled-components";

package/types/styles/utils/colors-export.d.ts

@@ -0,0 +1,73 @@
+/**
+ * Hand-written types for colors-export.js.
+ *
+ * ============================ WHY BY HAND ================================
+ * NEVER DERIVE THIS FROM THE .js WITH `keyof typeof`.
+ *
+ * It works locally, because the library compiles with `allowJs`. It collapses
+ * silently in the consumer, which does not: with no `allowJs`, TypeScript cannot
+ * read colors-export.js at all, `keyof typeof colors` degrades to
+ * `string | number | symbol` WITH NO DIAGNOSTIC, and `colors[name]` inside a
+ * template string then emits TS2731 — an error in OUR file, appearing only in
+ * THEIR build. A hand-written .d.ts resolves under every `moduleResolution` mode
+ * with or without `allowJs`.
+ *
+ * The cost is that this is a THIRD hand-maintained copy of the palette, beside
+ * src/styles/.config.scss and colors-export.js. That is what
+ * `npm run verify:palette` (scripts/ts-migration/verify-palette.cjs) is for: it
+ * makes drift a build failure rather than a silent `undefined` at runtime. Add a
+ * colour to the .js and this union without the other and the gate names it.
+ * =========================================================================
+ *
+ * src/styles stays .js permanently (playbook §A.1) and rollup copies the whole
+ * directory verbatim into the published `styles/` and `build/styles/` trees, so
+ * this file ships NEXT TO its .js and
+ * `@ntbjs/react-components/styles/utils/colors-export` gains types where it
+ * previously resolved none. A `.d.ts` is explicitly allowed by
+ * scripts/assert-no-published-typescript.cjs for exactly this reason; a `.ts`
+ * there would be raw TypeScript in a published package.
+ */
+
+/**
+ * Every registered design-token colour name.
+ *
+ * `theme.getColor` takes this union, so `getColor('emerald-999')` is a compile
+ * error instead of a `throw` from inside a styled template at runtime.
+ */
+export type ColorName =
+  | 'orange-600'
+  | 'orange-500'
+  | 'orange-400'
+  | 'emerald-600'
+  | 'emerald-500'
+  | 'emerald-400'
+  | 'emerald-300'
+  | 'emerald-200'
+  | 'gray-900'
+  | 'gray-800'
+  | 'gray-700'
+  | 'gray-600'
+  | 'gray-500'
+  | 'gray-400'
+  | 'gray-300'
+  | 'gray-200'
+  | 'gray-100'
+  | 'gray-50'
+  | 'cercise-500'
+  | 'cercise-400'
+  | 'cercise-300'
+  | 'cercise-200'
+  | 'cercise-100'
+  | 'red-600'
+  | 'red-500'
+  | 'red-200'
+  | 'brown-500'
+  | 'signal-yellow-500'
+  | 'signal-yellow-400'
+  | 'signal-green-500'
+  | 'signal-green-400'
+  | 'black'
+  | 'white';
+
+/** The palette itself: every `ColorName` mapped to a `#rrggbb` string. */
+export declare const colors: Record<ColorName, string>;

package/types/utils/dateTime.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Convert time given in miliseconds to a string representation of hours, minutes and seconds
+ * in the format HH:MM:SS
+ *
+ * The hours segment is omitted entirely for durations under an hour, so the
+ * result is `MM:SS` there — the `HH:` above is the maximal form, not a promise
+ * about width. Both call sites (`AssetGalleryGridCard`,
+ * `AssetGalleryCompactCard`) feed it straight into a `Badge`.
+ *
+ * @param ms duration in milliseconds. `number`, not `number | string`: the body
+ *           divides it, and a string would produce `NaN:NaN` rather than fail
+ */
+export declare const convertMsToHMS: (ms: number) => string;

package/types/utils/defaultTheme.d.ts

@@ -0,0 +1,174 @@
+import type { ColorName } from '../styles/utils/colors-export';
+import type { Interpolation, RuleSet } from 'styled-components';
+export type { ColorName };
+/**
+ * Looks up a design-token colour.
+ *
+ * Throws at runtime for an unregistered name, which is why the parameter is the
+ * closed `ColorName` union rather than `string`: the error moves from a runtime
+ * throw inside a styled template to a compile error at the call site.
+ */
+export type GetColor = (name: ColorName) => string;
+/**
+ * A value `themeProp` interpolates into the generated rule. Widened to
+ * styled-components' own `Interpolation` because that is literally what happens
+ * to it — six call sites in `Badge.styled.ts` and `Tabs.styled.ts` pass a
+ * `() => string` callback rather than a string, and two in `TextInput.styled.ts`
+ * pass numbers. The guarantee this type buys is ARITY, not value narrowness.
+ */
+export type ThemePropValue = Interpolation<object>;
+/**
+ * Emits one declaration three times — for `body.dark-theme`, for
+ * `body.light-theme`, and for neither-class-set with a
+ * `prefers-color-scheme: dark` fallback — so a single property can differ
+ * between themes.
+ *
+ * TWO REPO CONVENTIONS THE TYPE SYSTEM CANNOT ENFORCE, and both cause real
+ * visual bugs when broken:
+ *
+ * - **Never call `themeProp()` inside an `&::after` / `&::before` block.** The
+ *   generated `body.dark-theme &&` selector cannot address a pseudo-element from
+ *   inside one. Write the two rules out explicitly instead:
+ *   `body.light-theme &::after { … }` and `body.dark-theme &::after { … }`.
+ *
+ * - **Prefer static `&[data-x='state']` selectors over dynamic
+ *   `${props => css\`…\`}` rules for per-instance state.** Interpolated rules
+ *   share the component's `componentId`, so two instances in different states
+ *   collide and one wins for both.
+ *
+ * @param property   the CSS property, e.g. `color`, `background`, or a custom
+ *                   property like `--checkbox-black-box`
+ * @param darkMode   the value applied under `body.dark-theme`
+ * @param lightMode  the value applied under `body.light-theme`, and the fallback
+ *                   when neither class is present
+ * @param specificity how many `&` to repeat in the generated selector. A NUMBER —
+ *                   the implementation does `Array(specificity).fill('&')`, so a
+ *                   string silently produces a one-element array and specificity
+ *                   1. Typing it `number` is deliberate: it turns the one site
+ *                   that passes `'!important'` here into a compile error rather
+ *                   than blessing it.
+ */
+export type ThemeProp = (property: string, darkMode: ThemePropValue, lightMode: ThemePropValue, specificity?: number) => RuleSet<object>;
+/**
+ * Spacing scale. Consumed by react-select through its own `theme` prop as well
+ * as by our styled templates, which is why the member names are react-select's.
+ */
+export interface ThemeSpacing {
+    baseUnit: number;
+    controlHeight: number;
+    menuGutter: number;
+}
+/**
+ * react-select's colour contract, filled from our palette. These names are
+ * react-select's, not ours — do not rename them to design-token names.
+ */
+export interface ThemeColors {
+    primary: string;
+    primary75: string;
+    primary50: string;
+    primary25: string;
+    danger: string;
+    neutral0: string;
+    neutral5: string;
+    neutral10: string;
+    neutral20: string;
+    neutral30: string;
+    neutral40: string;
+    neutral50: string;
+    neutral60: string;
+    neutral70: string;
+    neutral80: string;
+    neutral90: string;
+}
+/**
+ * The whole theme, as a styled template sees it.
+ *
+ * Every member is REQUIRED, which is the truth inside an interpolation
+ * (`props.theme.getColor` is always there) and a constraint at the
+ * `<ThemeProvider>` boundary. Nothing in this repo hands over a partial theme —
+ * the only `ThemeProvider` is `.storybook/preview.js`, with the full
+ * `defaultTheme`. A consumer that wants to override part of it uses
+ * `PartialNtbTheme` + `applyDefaultTheme`, which is what every `.styled` file
+ * here does.
+ */
+export interface NtbTheme {
+    getColor: GetColor;
+    primaryFontFamily: string;
+    secondaryFontFamily: string;
+    themeProp: ThemeProp;
+    spacing: ThemeSpacing;
+    colors: ThemeColors;
+}
+/** A theme override: any subset of `NtbTheme`. */
+export type PartialNtbTheme = Partial<NtbTheme>;
+/**
+ * What `applyDefaultTheme` accepts.
+ *
+ * DELIBERATELY NOT `ExecutionProps & { theme?: PartialNtbTheme }`.
+ * `ExecutionProps['theme']` is `DefaultTheme | undefined`, and after the
+ * augmentation below `DefaultTheme` is `NtbTheme` with every member required —
+ * so intersecting makes the override required again and the function's own
+ * `theme = {}` default stops compiling (TS2322). Extra props still flow in
+ * fine: this is a parameter position, so a caller passing the full styled
+ * execution context is accepted and the runtime spreads the rest through
+ * unchanged.
+ */
+export interface ThemedProps {
+    theme?: PartialNtbTheme;
+}
+export declare const defaultTheme: {
+    getColor: (name: ColorName) => string;
+    primaryFontFamily: string;
+    secondaryFontFamily: string;
+    themeProp: typeof themeProp;
+    spacing: {
+        baseUnit: number;
+        controlHeight: number;
+        menuGutter: number;
+    };
+    colors: {
+        primary: string;
+        primary75: string;
+        primary50: string;
+        primary25: string;
+        danger: string;
+        neutral0: string;
+        neutral5: string;
+        neutral10: string;
+        neutral20: string;
+        neutral30: string;
+        neutral40: string;
+        neutral50: string;
+        neutral60: string;
+        neutral70: string;
+        neutral80: string;
+        neutral90: string;
+    };
+};
+/**
+ * Applies a different css property value for dark and light mode.
+ *
+ * Read `ThemeProp` above before changing the signature — its JSDoc carries the
+ * two conventions that the type system cannot enforce and that cause real
+ * visual bugs when broken.
+ */
+declare function themeProp(property: string, darkMode: ThemePropValue, lightMode: ThemePropValue, specificity?: number): RuleSet<object>;
+/**
+ * `.attrs()` helper: merges a caller's partial theme over `defaultTheme` so
+ * every interpolation can rely on the full contract.
+ *
+ * THE RETURN TYPE IS `{ theme: NtbTheme }` AND NOT `P & { theme: NtbTheme }`,
+ * ON PURPOSE. `attrs` merges its result OVER the incoming props, so a declared
+ * type only has to describe what this function CONTRIBUTES. Saying it also
+ * returns the caller's props re-declares them from a position that knows nothing
+ * about them, which is what produced the measured 25–31 TS2345 `.attrs()`
+ * assignability errors. The runtime still spreads the rest through — that part
+ * is unchanged, and 36 `.styled` files depend on it.
+ */
+export declare function applyDefaultTheme({ theme, ...props }: ThemedProps): {
+    theme: NtbTheme;
+};
+declare module 'styled-components' {
+    interface DefaultTheme extends NtbTheme {
+    }
+}

package/types/utils/getElementRef.d.ts

@@ -0,0 +1,21 @@
+import * as React from 'react';
+/**
+ * Reads a child element's `ref` across the peer range (`react >= 16.14`).
+ *
+ * `ref` is a regular prop only from React 19. Before that `createElement` moves it to
+ * `element.ref`, so reading `element.props.ref` silently returns `undefined` and the
+ * `cloneElement(children, { ref })` that follows destroys the child's ref.
+ *
+ * Neither location can be read unconditionally: React 19 warns on `element.ref`, React
+ * 18.3 warns on `props.ref`. Both warnings are `console.error`, which the stories gate
+ * fails on. The property SHAPE says which is live, measured on 19.2.4:
+ *
+ *   React 19, ref passed     props.ref data prop     element.ref warning getter
+ *   React 19, no ref         props.ref absent        element.ref data prop (null)
+ *   React <19                props.ref absent        element.ref data prop
+ *   React 18.3, ref passed   props.ref warning get   element.ref data prop
+ *
+ * Returning early on React 19's data-property `props.ref` is what keeps every branch off
+ * a warning getter.
+ */
+export declare function getElementRef(element: React.ReactElement): React.Ref<unknown> | null;

package/types/utils/parseTrigger.d.ts

@@ -0,0 +1,92 @@
+/**
+ * tippy's `trigger` space-string, parsed into the three discrete Floating UI
+ * interaction hooks.
+ *
+ * WHY THIS EXISTS AS A SEPARATE, PURE FUNCTION. tippy takes ONE prop —
+ * `trigger="mouseenter focus"` — and does its own tokenising
+ * (`splitBySpaces(instance.props.trigger).forEach(...)` in
+ * `tippy.js/dist/tippy.cjs.js`). Floating UI has no equivalent: it has three
+ * separate Hooks (`useClick`, `useHover`, `useFocus`), each with its own
+ * `enabled` flag. `Popover` and `Tooltip` both publish `trigger` as a documented
+ * prop and 62 consumer call sites pass it, so the string has to survive — which
+ * means exactly one place has to own the string → flags translation. This is it,
+ * and it is a pure function so it can be reasoned about (and later tested)
+ * without mounting anything.
+ *
+ * It lives in `src/utils/` rather than `src/hooks/` deliberately: it calls no
+ * Hook, has no React import, and `useFloatingPopover` is not its only plausible
+ * caller — a `<Popover>` that needs to know "does this trigger imply hover?" for
+ * a styling decision can ask without pulling in a Hook.
+ */
+/**
+ * Which Floating UI interaction Hooks a tippy trigger string turns on.
+ *
+ * All three are REQUIRED and always present. This is a computed result, not a
+ * bag of options: "the caller did not mention hover" and "hover is off" are the
+ * same statement here, and an optional member would let a caller write
+ * `if (parsed.hover === undefined)` as though there were a third state.
+ */
+export interface ParsedTrigger {
+    /** `click` token present → `useClick`. */
+    click: boolean;
+    /** `mouseenter` token present → `useHover`. */
+    hover: boolean;
+    /** `focus` or `focusin` token present → `useFocus`. */
+    focus: boolean;
+}
+/**
+ * tippy's own default, measured — `tippy.js/dist/tippy.cjs.js`:
+ *
+ * ```js
+ * var defaultProps = Object.assign({
+ *   …
+ *   trigger: 'mouseenter focus',
+ *   …
+ * }, pluginProps, renderProps);
+ * ```
+ *
+ * `Tooltip.tsx` declares no default for `trigger` and passes `undefined`
+ * straight through, so `undefined` HAS ALWAYS MEANT `'mouseenter focus'` for
+ * every tooltip in the library and in both consumers. `parseTrigger(undefined)`
+ * therefore has to return hover+focus, not nothing — see the `trigger`
+ * parameter's note.
+ *
+ * (`Popover.tsx` declares its own default, `'click focus'`, so it never relies
+ * on this one.)
+ */
+export declare const TIPPY_DEFAULT_TRIGGER = "mouseenter focus";
+/**
+ * Parses a tippy `trigger` prop into `{ click, hover, focus }`.
+ *
+ * THE THREE INPUTS THAT ARE EASY TO GET WRONG, all of them in use:
+ *
+ * - **`undefined`** (and `null`) means "tippy's default", i.e. hover+focus. It
+ *   does NOT mean "no triggers". Every `<Tooltip>` in the library that does not
+ *   pass `trigger` relies on this.
+ * - **`''`** means NO TRIGGERS AT ALL, and it is used. Measured, in BOTH
+ *   consumers — `mb-main-client/src/components/assets/sales_overlay.tsx:246` and
+ *   `ntb-dam/client/src/components/assets/sales_overlay.js:245`:
+ *
+ *   ```jsx
+ *   trigger={assetsHasAllRequiredData ? "" : "mouseenter focus"}
+ *   ```
+ *
+ *   i.e. `''` is how that call site turns the tooltip OFF conditionally. Return
+ *   anything truthy for it and a tooltip appears where the consumer suppressed
+ *   one. `''.split(/\s+/)` is `['']`, which is why the `filter(Boolean)`
+ *   below is load-bearing rather than tidiness — without it `''` would be
+ *   treated as an unrecognised token, which happens to give the same answer here
+ *   but would stop doing so the moment a token were matched loosely.
+ * - **A controlled popover ignores the result entirely.** That decision is NOT
+ *   made here: this function reports what the string says, and
+ *   `useFloatingPopover` is what gates the Hooks off when `visible` is a
+ *   boolean. Keeping the two apart means the parse stays testable and the
+ *   controlled-mode rule lives in one place instead of two.
+ *
+ * Whitespace is split on `/\s+/` and not `' '`, matching tippy's
+ * `splitBySpaces`, so `'click\n  focus'` parses the same way tippy parses it.
+ *
+ * @param trigger tippy's `trigger` prop. `undefined`/`null` → the tippy default
+ *                (`'mouseenter focus'`); `''` → nothing enabled
+ */
+export declare function parseTrigger(trigger?: string | null): ParsedTrigger;

package/build/_virtual/_rollupPluginBabelHelpers.js

@@ -1,12 +0,0 @@
-function _extends() {
-  return _extends = Object.assign ? Object.assign.bind() : function (n) {
-    for (var e = 1; e < arguments.length; e++) {
-      var t = arguments[e];
-      for (var r in t) ({}).hasOwnProperty.call(t, r) && (n[r] = t[r]);
-    }
-    return n;
-  }, _extends.apply(null, arguments);
-}
-
-export { _extends as extends };
-//# sourceMappingURL=_rollupPluginBabelHelpers.js.map

package/build/_virtual/_rollupPluginBabelHelpers.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"_rollupPluginBabelHelpers.js","sources":[],"sourcesContent":[],"names":[],"mappings":";;;;;;;;;;;;"}

package/build/widgets/AssetGallery/asset.propType.js

@@ -1,56 +0,0 @@
-import PropTypes from 'prop-types';
-
-const assetShape = {
-  key: PropTypes.oneOfType([PropTypes.string, PropTypes.number]).isRequired,
-  previewUrl: PropTypes.string,
-  title: PropTypes.string,
-  note: PropTypes.shape({
-    icon: PropTypes.element,
-    message: PropTypes.string
-  }),
-  width: PropTypes.number,
-  height: PropTypes.number,
-  fileType: PropTypes.oneOf(['image', 'video', 'pdf', 'file', 'audio']).isRequired,
-  fileTypeIconPosition: PropTypes.oneOf(['top-left', 'top-right']),
-  group: PropTypes.string,
-  actions: PropTypes.arrayOf(PropTypes.shape({
-    title: PropTypes.string.isRequired,
-    icon: PropTypes.element.isRequired,
-    onClick: PropTypes.func.isRequired,
-    className: PropTypes.shape,
-    component: PropTypes.func
-  })),
-  statusIcon: PropTypes.element,
-  overlay: PropTypes.element,
-  completed: PropTypes.bool,
-  hasError: PropTypes.bool,
-  disabled: PropTypes.bool,
-  onClick: PropTypes.func,
-  onContextMenu: PropTypes.func,
-  onMouseEnter: PropTypes.func,
-  instructionSeverity: PropTypes.oneOf([1, 2, 3, 4, 5]),
-  summary: PropTypes.shape({
-    title: PropTypes.string,
-    description: PropTypes.string,
-    instructions: PropTypes.string,
-    instructionSeverity: PropTypes.oneOf([1, 2, 3, 4, 5]),
-    headerLeft: PropTypes.node,
-    headerRight: PropTypes.node,
-    footerLeft: PropTypes.node,
-    footerRight: PropTypes.node
-  })
-};
-const assetShapeWithLayout = {
-  ...assetShape,
-  layout: PropTypes.shape({
-    width: PropTypes.number.isRequired,
-    height: PropTypes.number.isRequired,
-    translateX: PropTypes.number.isRequired,
-    translateY: PropTypes.number.isRequired,
-    type: PropTypes.oneOf(['groupLabel', 'asset']).isRequired,
-    hasHeightAndWidth: PropTypes.bool
-  }).isRequired
-};
-
-export { assetShape, assetShapeWithLayout };
-//# sourceMappingURL=asset.propType.js.map

package/build/widgets/AssetGallery/asset.propType.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"asset.propType.js","sources":["../../../src/components/widgets/AssetGallery/asset.propType.js"],"sourcesContent":["import PropTypes from 'prop-types';\n\nexport const assetShape = {\n  key: PropTypes.oneOfType([PropTypes.string, PropTypes.number]).isRequired,\n  previewUrl: PropTypes.string,\n  title: PropTypes.string,\n  note: PropTypes.shape({\n    icon: PropTypes.element,\n    message: PropTypes.string\n  }),\n  width: PropTypes.number,\n  height: PropTypes.number,\n  fileType: PropTypes.oneOf(['image', 'video', 'pdf', 'file', 'audio']).isRequired,\n  fileTypeIconPosition: PropTypes.oneOf(['top-left', 'top-right']),\n  group: PropTypes.string,\n  actions: PropTypes.arrayOf(\n    PropTypes.shape({\n      title: PropTypes.string.isRequired,\n      icon: PropTypes.element.isRequired,\n      onClick: PropTypes.func.isRequired,\n      className: PropTypes.shape,\n      component: PropTypes.func\n    })\n  ),\n  statusIcon: PropTypes.element,\n  overlay: PropTypes.element,\n  completed: PropTypes.bool,\n  hasError: PropTypes.bool,\n  disabled: PropTypes.bool,\n  onClick: PropTypes.func,\n  onContextMenu: PropTypes.func,\n  onMouseEnter: PropTypes.func,\n  instructionSeverity: PropTypes.oneOf([1, 2, 3, 4, 5]),\n  summary: PropTypes.shape({\n    title: PropTypes.string,\n    description: PropTypes.string,\n    instructions: PropTypes.string,\n    instructionSeverity: PropTypes.oneOf([1, 2, 3, 4, 5]),\n    headerLeft: PropTypes.node,\n    headerRight: PropTypes.node,\n    footerLeft: PropTypes.node,\n    footerRight: PropTypes.node\n  })\n};\n\nexport const assetShapeWithLayout = {\n  ...assetShape,\n  layout: PropTypes.shape({\n    width: PropTypes.number.isRequired,\n    height: PropTypes.number.isRequired,\n    translateX: PropTypes.number.isRequired,\n    translateY: PropTypes.number.isRequired,\n    type: PropTypes.oneOf(['groupLabel', 'asset']).isRequired,\n    hasHeightAndWidth: PropTypes.bool\n  }).isRequired\n};\n"],"names":["assetShape","key","PropTypes","oneOfType","string","number","isRequired","previewUrl","title","note","shape","icon","element","message","width","height","fileType","oneOf","fileTypeIconPosition","group","actions","arrayOf","onClick","func","className","component","statusIcon","overlay","completed","bool","hasError","disabled","onContextMenu","onMouseEnter","instructionSeverity","summary","description","instructions","headerLeft","node","headerRight","footerLeft","footerRight","assetShapeWithLayout","layout","translateX","translateY","type","hasHeightAndWidth"],"mappings":";;AAEO,MAAMA,UAAU,GAAG;AACxBC,EAAAA,GAAG,EAAEC,SAAS,CAACC,SAAS,CAAC,CAACD,SAAS,CAACE,MAAM,EAAEF,SAAS,CAACG,MAAM,CAAC,CAAC,CAACC,UAAU;EACzEC,UAAU,EAAEL,SAAS,CAACE,MAAM;EAC5BI,KAAK,EAAEN,SAAS,CAACE,MAAM;AACvBK,EAAAA,IAAI,EAAEP,SAAS,CAACQ,KAAK,CAAC;IACpBC,IAAI,EAAET,SAAS,CAACU,OAAO;IACvBC,OAAO,EAAEX,SAAS,CAACE,MAAAA;AACrB,GAAC,CAAC;EACFU,KAAK,EAAEZ,SAAS,CAACG,MAAM;EACvBU,MAAM,EAAEb,SAAS,CAACG,MAAM;AACxBW,EAAAA,QAAQ,EAAEd,SAAS,CAACe,KAAK,CAAC,CAAC,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,CAAC,CAAC,CAACX,UAAU;EAChFY,oBAAoB,EAAEhB,SAAS,CAACe,KAAK,CAAC,CAAC,UAAU,EAAE,WAAW,CAAC,CAAC;EAChEE,KAAK,EAAEjB,SAAS,CAACE,MAAM;EACvBgB,OAAO,EAAElB,SAAS,CAACmB,OAAO,CACxBnB,SAAS,CAACQ,KAAK,CAAC;AACdF,IAAAA,KAAK,EAAEN,SAAS,CAACE,MAAM,CAACE,UAAU;AAClCK,IAAAA,IAAI,EAAET,SAAS,CAACU,OAAO,CAACN,UAAU;AAClCgB,IAAAA,OAAO,EAAEpB,SAAS,CAACqB,IAAI,CAACjB,UAAU;IAClCkB,SAAS,EAAEtB,SAAS,CAACQ,KAAK;IAC1Be,SAAS,EAAEvB,SAAS,CAACqB,IAAAA;AACvB,GAAC,CACH,CAAC;EACDG,UAAU,EAAExB,SAAS,CAACU,OAAO;EAC7Be,OAAO,EAAEzB,SAAS,CAACU,OAAO;EAC1BgB,SAAS,EAAE1B,SAAS,CAAC2B,IAAI;EACzBC,QAAQ,EAAE5B,SAAS,CAAC2B,IAAI;EACxBE,QAAQ,EAAE7B,SAAS,CAAC2B,IAAI;EACxBP,OAAO,EAAEpB,SAAS,CAACqB,IAAI;EACvBS,aAAa,EAAE9B,SAAS,CAACqB,IAAI;EAC7BU,YAAY,EAAE/B,SAAS,CAACqB,IAAI;AAC5BW,EAAAA,mBAAmB,EAAEhC,SAAS,CAACe,KAAK,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC,CAAC;AACrDkB,EAAAA,OAAO,EAAEjC,SAAS,CAACQ,KAAK,CAAC;IACvBF,KAAK,EAAEN,SAAS,CAACE,MAAM;IACvBgC,WAAW,EAAElC,SAAS,CAACE,MAAM;IAC7BiC,YAAY,EAAEnC,SAAS,CAACE,MAAM;AAC9B8B,IAAAA,mBAAmB,EAAEhC,SAAS,CAACe,KAAK,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC,CAAC;IACrDqB,UAAU,EAAEpC,SAAS,CAACqC,IAAI;IAC1BC,WAAW,EAAEtC,SAAS,CAACqC,IAAI;IAC3BE,UAAU,EAAEvC,SAAS,CAACqC,IAAI;IAC1BG,WAAW,EAAExC,SAAS,CAACqC,IAAAA;GACxB,CAAA;AACH,EAAC;AAEM,MAAMI,oBAAoB,GAAG;AAClC,EAAA,GAAG3C,UAAU;AACb4C,EAAAA,MAAM,EAAE1C,SAAS,CAACQ,KAAK,CAAC;AACtBI,IAAAA,KAAK,EAAEZ,SAAS,CAACG,MAAM,CAACC,UAAU;AAClCS,IAAAA,MAAM,EAAEb,SAAS,CAACG,MAAM,CAACC,UAAU;AACnCuC,IAAAA,UAAU,EAAE3C,SAAS,CAACG,MAAM,CAACC,UAAU;AACvCwC,IAAAA,UAAU,EAAE5C,SAAS,CAACG,MAAM,CAACC,UAAU;AACvCyC,IAAAA,IAAI,EAAE7C,SAAS,CAACe,KAAK,CAAC,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC,CAACX,UAAU;IACzD0C,iBAAiB,EAAE9C,SAAS,CAAC2B,IAAAA;AAC/B,GAAC,CAAC,CAACvB,UAAAA;AACL;;;;"}