@eifi1/ui-kit 0.54.0 → 0.55.0

package/src/rhf/form-core.tsx

@@ -1,324 +0,0 @@
-/**
- * The react-hook-form adapter: the five parts every bound field is built from, and the
- * hook they share. Behind `@eifi1/ui-kit/rhf`, which exports `Form` alone of them.
- *
- * The kit's own module since 0.34 (refactor audit 2026-10, API-6f): the bound `Rhf*`
- * fields and `RhfField` build on these parts, and import them from here. ./form is the
- * public face — `Form`; the parts left the public surface in 0.35 (deprecated in 0.34),
- * when no app imported them any more.
- *
- * ```tsx
- * <Form {...form}>
- *   <FormField control={form.control} name="amount" render={({ field }) => (
- *     <FormItem>
- *       <FormLabel required>Amount</FormLabel>
- *       <FormControl>
- *         <NumberField value={field.value} onCommit={field.onChange} />
- *       </FormControl>
- *       <FormMessage />
- *     </FormItem>
- *   )} />
- * </Form>
- * ```
- *
- * The shape is shadcn's `form.tsx`, on purpose: Kastlan builds every form from that
- * file, so moving onto this one is an import line rather than a rewrite. What differs
- * is what the shadcn file gets wrong:
- *
- *  - **`aria-describedby` names only what is on screen.** shadcn always points the
- *    control at a description id, rendered or not, and at the message id whenever the
- *    field has an error, whether a message was rendered for it or not. A reference to
- *    a node that does not exist describes the field as nothing. Here the description
- *    and the message say when they are mounted, and the control points at exactly
- *    those.
- *  - **Merged, never replaced.** A control that already carries its own
- *    `aria-describedby` keeps it, first — the same rule as the kit's `error` prop
- *    (see `useFieldError` in components/field-parts.tsx).
- *  - **No Radix.** `FormControl` is a one-child `cloneElement`, not `Slot`, and the
- *    label is the kit's own `Label` — the kit carries no Radix dependency and this
- *    entry is not the place to start.
- *
- * ## Why this is its own entry
- *
- * The main barrel once shipped a react-hook-form hook (`use-rhf-wizard-step`) and
- * removed it: it made react-hook-form an install every consumer's typecheck paid for,
- * for a hook nobody called (see the wizard section of src/index.ts). This is the
- * answer to that, not a reversal of it. Nothing outside `src/rhf*` imports
- * react-hook-form — `__tests__/packaging-contract.test.ts` holds that — and the peer is
- * optional, so an app that does not use it installs nothing and imports nothing.
- *
- * ## Painting the field
- *
- * `FormControl` sets `aria-invalid` on its child. `NumberField` and the pickers paint
- * from that attribute; `Input`, `Select` and `Textarea` paint only from their
- * `invalid` prop (see its note in components/field-base.tsx: a bare attribute announces but
- * does not paint), so pass it from the render prop —
- * `<Input {...field} invalid={fieldState.invalid} />`. `FormControl` does not inject
- * `invalid` itself because its child may be a native element, which would print it
- * into the DOM as an unknown attribute.
- *
- * ## Clearing a picker: `null`, unless the picker is told otherwise
- *
- * Nothing here touches a value. `FormField` is `Controller`, so what a control hands
- * `field.onChange` is exactly what lands in the form — and what the entity pickers
- * hand it on a clear is `null`: `EntityCombobox`'s "×", `InlineEntityCombobox`'s "×"
- * and its emptied text. (`MultiEntityCombobox` and `MultiSelect` clear to `[]`.)
- *
- * A zod schema that spells "no choice" as `""` (`z.string()`, or `z.literal("")` in a
- * union) then fails on the `null`. Say so on the PICKER, not here:
- *
- * ```tsx
- * <EntityCombobox clearValue="" value={field.value} onChange={field.onChange} … />
- * ```
- *
- * `clearValue` also types `onChange` (`(v: V | "") => void` rather than
- * `V | null`) and reads `""` back as "nothing selected", so an initial `defaultValues`
- * of `""` shows the placeholder rather than an unresolvable id. The adapter does not
- * coerce because it cannot see the schema: mapping `null` to `""` for every field
- * would break every schema that wants `null` (`z.string().nullable()`), which is the
- * pickers' default for a reason — it is the one value no option can have.
- */
-import {
-  Children,
-  cloneElement,
-  createContext,
-  isValidElement,
-  useCallback,
-  useContext,
-  useId,
-  useLayoutEffect,
-  useMemo,
-  useState,
-  type ComponentProps,
-  type ReactElement,
-} from "react";
-import {
-  Controller,
-  FormProvider,
-  useFormContext,
-  useFormState,
-  type ControllerProps,
-  type FieldPath,
-  type FieldValues,
-} from "react-hook-form";
-import { Label, type LabelProps } from "../components/field-base";
-import { cn } from "../lib/cn";
-
-/** The form's `useForm()` return, spread in: `<Form {...form}>`. react-hook-form's own
- *  `FormProvider`, under the name the shadcn file gave it. */
-export const Form = FormProvider;
-
-// ── contexts ─────────────────────────────────────────────────────────────────
-
-const FormFieldContext = createContext<{ name: string } | null>(null);
-
-/** The two optional nodes a control can be described by. */
-type Described = "description" | "message";
-
-interface FormItemContextValue {
-  id: string;
-  mounted: Record<Described, boolean>;
-  mark: (slot: Described, on: boolean) => void;
-}
-
-const FormItemContext = createContext<FormItemContextValue | null>(null);
-
-// ── FormField ────────────────────────────────────────────────────────────────
-
-/**
- * react-hook-form's `Controller`, with the field's name put in context for the parts
- * below it. Takes exactly `Controller`'s props.
- */
-export function FormField<
-  TFieldValues extends FieldValues = FieldValues,
-  TName extends FieldPath<TFieldValues> = FieldPath<TFieldValues>,
-  TTransformedValues = TFieldValues,
->(props: ControllerProps<TFieldValues, TName, TTransformedValues>) {
-  const value = useMemo(() => ({ name: props.name as string }), [props.name]);
-  return (
-    <FormFieldContext.Provider value={value}>
-      <Controller {...props} />
-    </FormFieldContext.Provider>
-  );
-}
-
-// ── useFormField ─────────────────────────────────────────────────────────────
-
-/**
- * The ids and the state of the field around the caller: for a part of your own that
- * sits beside the kit's (a character counter that belongs in `aria-describedby`, a
- * label with a different look).
- *
- * Throws outside a `FormField` + `FormItem` pair. shadcn's version answered there with
- * ids like `undefined-form-item`, which label nothing and fail nowhere.
- */
-export function useFormField() {
-  const field = useContext(FormFieldContext);
-  const item = useContext(FormItemContext);
-  if (!field) throw new Error("useFormField must be used inside <FormField>.");
-  if (!item) throw new Error("useFormField must be used inside <FormItem>.");
-  const { getFieldState } = useFormContext();
-  // Subscribes this part to the field's state, so a label or message re-renders when
-  // the field's error changes without the whole form doing so.
-  const formState = useFormState({ name: field.name });
-  const state = getFieldState(field.name, formState);
-  const formDescriptionId = `${item.id}-description`;
-  const formMessageId = `${item.id}-message`;
-  const describedBy = [item.mounted.description && formDescriptionId, item.mounted.message && formMessageId]
-    .filter(Boolean)
-    .join(" ");
-  return {
-    id: item.id,
-    name: field.name,
-    formItemId: `${item.id}-control`,
-    formDescriptionId,
-    formMessageId,
-    /** The ids of the description and message that are actually rendered, or
-     *  `undefined` when neither is. */
-    describedBy: describedBy || undefined,
-    ...state,
-  };
-}
-
-// ── FormItem ─────────────────────────────────────────────────────────────────
-
-export type FormItemProps = ComponentProps<"div">;
-
-/** One field's box: mints the id its label, control, description and message share. */
-export function FormItem({ className, ...rest }: FormItemProps) {
-  const id = useId();
-  const [mounted, setMounted] = useState<Record<Described, boolean>>({
-    description: false,
-    message: false,
-  });
-  const mark = useCallback(
-    (slot: Described, on: boolean) => setMounted((prev) => (prev[slot] === on ? prev : { ...prev, [slot]: on })),
-    [],
-  );
-  const value = useMemo(() => ({ id, mounted, mark }), [id, mounted, mark]);
-  return (
-    <FormItemContext.Provider value={value}>
-      {/* `content-start`: stretched to a taller neighbour's height in a grid row, the
-          item gave the extra to its rows and its control sat lower (showcase audit). */}
-      <div data-slot="form-item" {...rest} className={cn("grid content-start gap-1", className)} />
-    </FormItemContext.Provider>
-  );
-}
-
-/** Report a describing node's presence to the item, so the control points at it only
- *  while it is on screen. A layout effect, so the reference lands before paint. */
-function useDescribes(slot: Described, on: boolean) {
-  const item = useContext(FormItemContext);
-  const mark = item?.mark;
-  useLayoutEffect(() => {
-    if (!on || !mark) return;
-    mark(slot, true);
-    return () => mark(slot, false);
-  }, [slot, on, mark]);
-}
-
-// ── FormLabel ────────────────────────────────────────────────────────────────
-
-export type FormLabelProps = LabelProps;
-
-/**
- * The kit's {@link Label}, bound to the control by `htmlFor` and turned to the danger
- * colour while the field is invalid. `required` draws the kit's `aria-hidden` mark:
- * whether the field is required is the control's to announce.
- */
-export function FormLabel({ className, ...rest }: FormLabelProps) {
-  const { error, formItemId } = useFormField();
-  return (
-    <Label
-      data-slot="form-label"
-      data-error={error ? true : undefined}
-      htmlFor={formItemId}
-      {...rest}
-      className={cn("data-[error=true]:text-danger", className)}
-    />
-  );
-}
-
-// ── FormControl ──────────────────────────────────────────────────────────────
-
-export interface FormControlProps {
-  /** Exactly one element: the kit field, or a native one. It receives `id`,
-   *  `aria-describedby` and `aria-invalid`. */
-  children: ReactElement;
-}
-
-type AriaProps = {
-  id?: string;
-  "aria-describedby"?: string;
-  "aria-invalid"?: ComponentProps<"input">["aria-invalid"];
-};
-
-/**
- * Wires its one child to the item: the `id` the label points at, `aria-describedby`
- * naming the rendered description and message, and `aria-invalid` while the field has
- * an error.
- *
- * The child's own values win where it has them (an explicit `id`, a set
- * `aria-invalid`), as they did under Radix `Slot`; its own `aria-describedby` is
- * merged in front of the item's rather than replaced.
- */
-export function FormControl({ children }: FormControlProps) {
-  const { invalid, formItemId, describedBy } = useFormField();
-  const child = Children.only(children);
-  if (!isValidElement<AriaProps>(child)) return child;
-  const own = child.props;
-  const merged = [own["aria-describedby"], describedBy].filter(Boolean).join(" ");
-  return cloneElement(child, {
-    id: own.id ?? formItemId,
-    "aria-describedby": merged || undefined,
-    "aria-invalid": own["aria-invalid"] ?? (invalid || undefined),
-  });
-}
-
-// ── FormDescription / FormMessage ────────────────────────────────────────────
-
-export type FormDescriptionProps = ComponentProps<"p">;
-
-/** Standing advice under the field ("at least twelve characters"). */
-export function FormDescription({ className, ...rest }: FormDescriptionProps) {
-  const { formDescriptionId } = useFormField();
-  useDescribes("description", true);
-  return (
-    <p
-      data-slot="form-description"
-      {...rest}
-      id={formDescriptionId}
-      className={cn("text-caption leading-tight text-muted", className)}
-    />
-  );
-}
-
-export type FormMessageProps = ComponentProps<"p">;
-
-/**
- * The field's error message, from the form — the kit renders no string of its own
- * here; the schema or the `rules` carry the words. Without an error it renders its
- * `children`, if any, and otherwise nothing.
- *
- * Deliberately NOT `role="alert"`, for the reason the kit's `error` prop gives: the
- * message is read when focus reaches the control, which is where a field's own error
- * is wanted, and an alert would interrupt on every keystroke of a form that
- * re-validates as you type.
- */
-export function FormMessage({ className, children, ...rest }: FormMessageProps) {
-  const { error, formMessageId } = useFormField();
-  const body = error ? String(error.message ?? "") : children;
-  const shown = body !== undefined && body !== null && body !== false && body !== "";
-  useDescribes("message", shown);
-  if (!shown) return null;
-  return (
-    <p
-      data-slot="form-message"
-      {...rest}
-      id={formMessageId}
-      className={cn("text-caption leading-tight text-danger", className)}
-    >
-      {body}
-    </p>
-  );
-}

package/src/rhf/form.tsx

@@ -1,12 +0,0 @@
-/**
- * `Form` — the public face of ./form-core, where the shadcn scaffold the bound fields are
- * built from lives (its header has the whole story: what differs from shadcn's file, why
- * /rhf is its own entry, how a picker clears).
- *
- * The scaffold itself (`FormField`, `useFormField`, `FormItem`, `FormLabel`, `FormControl`,
- * `FormDescription`, `FormMessage` and five props types) was public until 0.35 (refactor
- * audit 2026-10, API-6f; deprecated in 0.34): no app builds a form from it any more.
- * kastlan, the one /rhf consumer, uses `Form`, the bound `Rhf*` fields and `RhfField` for
- * a control of its own — the same parts, folded into one element.
- */
-export { Form } from "./form-core";

package/src/rhf/line-items.tsx

@@ -1,135 +0,0 @@
-/**
- * {@link LineItems} over react-hook-form's `useFieldArray`. `@eifi1/ui-kit/rhf`.
- *
- * ```tsx
- * <RhfLineItems
- *   name="components"
- *   newItem={() => ({ type: "net_rent", amount: null, validFrom: "" })}
- *   minItems={1}
- *   columns={[
- *     { key: "type", header: "Type", render: ({ name, label }) => (
- *       <RhfSelect name={`${name}.type`} options={TYPES} aria-label={label} />
- *     ) },
- *     { key: "amount", header: "Amount", width: "8rem", align: "end", render: ({ name, label }) => (
- *       <RhfMoneyField name={`${name}.amount`} aria-label={label} />
- *     ) },
- *   ]}
- *   totals={{ amount: formatMoney(total) }}
- * />
- * ```
- *
- * The rows are the array's `fields` (keyed by their `id`, as react-hook-form asks),
- * Add appends `newItem()`, remove is `remove(index)`, and an error on the array
- * itself — the `rules` here, or a resolver's `lines: "At least two lines"` — is the
- * list's `error`. Each cell's `render` gets `name`, the row's path
- * (`"components.2"`), to bind its field to.
- *
- * `summary`, `fieldLabels`, `narrowColumns`, `removePlacement` and `removeAlign` pass
- * through to {@link LineItems}. With
- * `fieldLabels="floating"` a cell's `fieldLabel` is the column's name; the bound
- * fields' own `label` is a label ABOVE the control, so for the floating
- * one render the kit field through `RhfField`:
- * `render={({ field, invalid }) => <Input label={fieldLabel} aria-label={label} {...field} invalid={invalid} />}`.
- */
-import type { ReactNode } from "react";
-import {
-  useFieldArray,
-  useFormState,
-  type FieldArray,
-  type FieldArrayPath,
-  type FieldArrayWithId,
-  type FieldValues,
-  type UseFieldArrayProps,
-} from "react-hook-form";
-import {
-  LineItems,
-  type LineItemCellContext,
-  type LineItemsColumn,
-  type LineItemsProps,
-} from "../components/line-items";
-
-/** A cell's context, with the row's path in the form. */
-export interface RhfLineItemCellContext<TItem, TArrayName extends string> extends LineItemCellContext<TItem> {
-  /** The row's path: `${name}.${index}` — bind the cell's field to
-   *  `` `${name}.amount` ``. */
-  name: `${TArrayName}.${number}`;
-}
-
-export interface RhfLineItemsColumn<TItem, TArrayName extends string> extends Omit<LineItemsColumn<TItem>, "render"> {
-  render: (ctx: RhfLineItemCellContext<TItem, TArrayName>) => ReactNode;
-}
-
-export interface RhfLineItemsProps<
-  TFieldValues extends FieldValues = FieldValues,
-  TArrayName extends FieldArrayPath<TFieldValues> = FieldArrayPath<TFieldValues>,
-  TTransformed = TFieldValues,
-> extends Omit<
-  LineItemsProps<FieldArrayWithId<TFieldValues, TArrayName, "id">>,
-  "items" | "columns" | "onAdd" | "onRemove" | "getKey"
-> {
-  name: TArrayName;
-  /** `form.control`. Optional under `<Form {...form}>`. */
-  control?: UseFieldArrayProps<TFieldValues, TArrayName, "id", TTransformed>["control"];
-  /** `useFieldArray`'s `rules` (`minLength`, `validate` …); its message is the list's
-   *  error. */
-  rules?: UseFieldArrayProps<TFieldValues, TArrayName, "id", TTransformed>["rules"];
-  columns: readonly RhfLineItemsColumn<FieldArrayWithId<TFieldValues, TArrayName, "id">, TArrayName>[];
-  /** A new row's values. Omitted: no add button. */
-  newItem?: () => FieldArray<TFieldValues, TArrayName>;
-  /** `false`: no remove buttons. Default `true`. */
-  removable?: boolean;
-}
-
-/** The message of an error at `path` in react-hook-form's errors tree: the array's
- *  own (`root`, from `rules`) or one a resolver put on the array. */
-function arrayError(errors: unknown, path: string): string | undefined {
-  let node: unknown = errors;
-  for (const key of path.split(".")) {
-    if (node === null || typeof node !== "object") return undefined;
-    node = (node as Record<string, unknown>)[key];
-  }
-  if (node === null || typeof node !== "object") return undefined;
-  const { root, message } = node as { root?: { message?: unknown }; message?: unknown };
-  const text = root?.message ?? message;
-  return typeof text === "string" && text !== "" ? text : undefined;
-}
-
-/** {@link LineItems} bound to a field array. See the module note. */
-export function RhfLineItems<
-  TFieldValues extends FieldValues = FieldValues,
-  TArrayName extends FieldArrayPath<TFieldValues> = FieldArrayPath<TFieldValues>,
-  TTransformed = TFieldValues,
->({
-  name,
-  control,
-  rules,
-  columns,
-  newItem,
-  removable = true,
-  error,
-  ...rest
-}: RhfLineItemsProps<TFieldValues, TArrayName, TTransformed>) {
-  const { fields, append, remove } = useFieldArray<TFieldValues, TArrayName, "id", TTransformed>({
-    control,
-    name,
-    rules,
-  });
-  const { errors } = useFormState({ control, name: name as never });
-  const bound: LineItemsColumn<FieldArrayWithId<TFieldValues, TArrayName, "id">>[] = columns.map(
-    ({ render, ...column }) => ({
-      ...column,
-      render: (ctx) => render({ ...ctx, name: `${name}.${ctx.index}` as `${TArrayName}.${number}` }),
-    }),
-  );
-  return (
-    <LineItems
-      {...rest}
-      items={fields}
-      columns={bound}
-      getKey={(field) => field.id}
-      onAdd={newItem ? () => append(newItem()) : undefined}
-      onRemove={removable ? (index) => remove(index) : undefined}
-      error={error ?? arrayError(errors, name)}
-    />
-  );
-}

package/src/rhf/use-rhf-wizard-step.ts

@@ -1,104 +0,0 @@
-/**
- * The bridge between a react-hook-form step and the wizard's Next gate.
- * `@eifi1/ui-kit/rhf`.
- *
- * ```tsx
- * function AddressStep({ onUpdate }: { onUpdate: (v: Address) => void }) {
- *   const form = useForm<Address>({ defaultValues });
- *   useRhfWizardStep(form, { onValid: onUpdate });
- *   return <Form {...form}>…</Form>;
- * }
- * ```
- *
- * Inside a `<StepperNav>` the hook registers the step's validator with the wizard, so
- * Next (and Finish on a form-bearing last step) runs it: on success the values go to
- * `onValid` and the wizard advances; on failure the bound fields show their inline
- * messages, react-hook-form focuses the first field in error, and the wizard stays
- * put — and, since the result carries no per-field errors, says its "fill in the
- * required fields" line so the button did not seem to do nothing. It also RETURNS the
- * validator, for a nav of your own outside `<StepperNav>` (where there is no wizard
- * context to register with, so nothing is registered).
- *
- * Two modes:
- *
- *  - **The whole form** (no `fields`): `form.handleSubmit`, exactly as kastlan's
- *    `use-rhf-wizard-step.ts` — every rule and the resolver run, `onValid` receives
- *    the TRANSFORMED values (a zod `.transform()` included), and focus follows the
- *    form's own `shouldFocusError` (on by default).
- *  - **Some fields** (`fields: ["iban", "bic"]`): `form.trigger(fields)`, for a wizard
- *    that keeps one form across several steps, each of which validates only what it
- *    shows. The first of those fields in error is focused (`shouldFocus`; the control
- *    has to take `field.ref`), errors on fields of later steps are not raised, and
- *    `onValid` receives `form.getValues()` — the untransformed values, because a
- *    resolver's output is only produced for the whole form.
- *
- * Both callbacks are read through refs, so the validator is registered once per form
- * however the caller writes them (an inline `(v) => onUpdate(v)` is the usual case).
- *
- * The positional `useRhfWizardStep(form, onValid)` of the hook kastlan kept is the
- * whole-form mode, and still accepted.
- *
- * Why it lives here and not in `@eifi1/ui-kit/wizard`: it imports react-hook-form,
- * which only this entry may (see packaging-contract).
- */
-import { useCallback, useEffect, useRef } from "react";
-import type { FieldPath, FieldValues, UseFormReturn } from "react-hook-form";
-import { useOptionalWizardContext } from "../wizard/wizard-context";
-
-export type RhfWizardStepOptions<TFieldValues extends FieldValues, TTransformed = TFieldValues> =
-  | {
-      /** Validate only these fields — the step's share of a form that spans steps. */
-      fields: readonly FieldPath<TFieldValues>[];
-      /** Called with `form.getValues()` when the fields pass, before the wizard
-       *  advances. */
-      onValid?: (values: TFieldValues) => void;
-    }
-  | {
-      /** Omitted: validate the whole form through `handleSubmit`. */
-      fields?: undefined;
-      /** Called with the form's (transformed) values when it passes, before the
-       *  wizard advances. */
-      onValid?: (values: TTransformed) => void;
-    };
-
-/**
- * Connects `form` to the wizard's step validation and returns the step's validator.
- * See the module note for the two modes.
- */
-export function useRhfWizardStep<TFieldValues extends FieldValues, TContext = unknown, TTransformed = TFieldValues>(
-  form: UseFormReturn<TFieldValues, TContext, TTransformed>,
-  options?: RhfWizardStepOptions<TFieldValues, TTransformed> | ((values: TTransformed) => void),
-): () => Promise<boolean> {
-  const opts = typeof options === "function" ? { onValid: options } : (options ?? {});
-  const optsRef = useRef(opts);
-  useEffect(() => {
-    optsRef.current = opts;
-  });
-
-  const validate = useCallback(async (): Promise<boolean> => {
-    const current = optsRef.current;
-    if (current.fields) {
-      const ok = await form.trigger([...current.fields], { shouldFocus: true });
-      if (ok) current.onValid?.(form.getValues());
-      return ok;
-    }
-    const onValid = current.onValid as ((values: TTransformed) => void) | undefined;
-    let ok = false;
-    await form.handleSubmit(
-      (values) => {
-        ok = true;
-        onValid?.(values);
-      },
-      () => {
-        ok = false;
-      },
-    )();
-    return ok;
-  }, [form]);
-
-  const wizard = useOptionalWizardContext();
-  const register = wizard?.registerStepValidate;
-  useEffect(() => register?.(validate), [register, validate]);
-
-  return validate;
-}

package/src/rhf.ts

@@ -1,21 +0,0 @@
-// `@eifi1/ui-kit/rhf` — the react-hook-form adapter: Form and the bound Rhf* fields (and
-// RhfField as the escape hatch). The shadcn scaffold they are built from (FormField,
-// FormItem, FormLabel, FormControl, FormDescription, FormMessage, useFormField) left the
-// surface in 0.35 (refactor audit 2026-10, API-6f; deprecated in 0.34).
-//
-// The only entry point in the package that requires `react-hook-form`, and an optional
-// peer for that reason: an app without a form library installs nothing for it. NOT
-// re-exported from the main barrel, which would make the peer everyone's — the reason
-// the barrel dropped its last react-hook-form import (see the wizard section of
-// src/index.ts). The packaging contract test holds that line.
-export * from "./rhf/form";
-// The react-hook-form bridge to the wizard's Next gate (useWizard lives in /wizard).
-export * from "./rhf/use-rhf-wizard-step";
-// Bound fields — one line per field (RhfTextField, RhfNumberField, RhfIntegerField, RhfMoneyField,
-// RhfDateField, RhfTextarea, RhfSelect, RhfCheckbox, RhfCombobox, RhfTextCombobox; 0.22: RhfTimeInput,
-// RhfDateRangePicker, RhfToggleGroup, RhfIbanInput, RhfPhoneInput; 0.23: RhfCountrySelect,
-// RhfMonthPicker; 0.24: RhfInlineEntityCombobox)
-// and RhfField, the shell they are built on.
-export * from "./rhf/fields";
-// LineItems over useFieldArray.
-export * from "./rhf/line-items";

package/src/search/command-palette-labels.ts

@@ -1,16 +0,0 @@
-// The English words of ./command-palette, in a module with no component code: the English
-// catalogue (src/i18n/defaults.ts) imports them without the component, so `en` loads as one
-// chunk like the other languages (0.34, KS U8). ./command-palette re-exports them.
-
-import type { CommandPaletteLabels } from "./command-palette";
-
-export const DEFAULT_COMMAND_PALETTE_LABELS: CommandPaletteLabels = {
-  placeholder: "Search…",
-  empty: "No results",
-  loading: "Searching…",
-  dialog: "Search",
-  error: "Search failed. Try again.",
-  clear: "Clear search",
-  submit: "Search",
-  close: "Close",
-};