react-luna-form 0.0.86 → 0.0.87

package/dist/types/luna-react/src/client/lib/host-value-store.d.ts

@@ -2,6 +2,13 @@ import type { Nullable } from '../../../../luna-core/index';
 export declare const hostValueAtom: import("jotai").PrimitiveAtom<Nullable<Record<string, unknown>>> & {
     init: Nullable<Record<string, unknown>>;
 };
+/** What the host says about one field, with the sentinel already read. */
+export type HostEntry = {
+    /** The host names this field. A field it does not name reads `undefined`. */
+    found: boolean;
+    value: unknown;
+};
+export declare function readHostEntry(entry: unknown): HostEntry;
 /**
  * One field's entry in that record.
  *
@@ -12,19 +19,10 @@ export declare const hostValueAtom: import("jotai").PrimitiveAtom<Nullable<Recor
  * read; doing it at the call site is what keeps this correct where a memo
  * comparator could not be. See `ListPathContext`.
  *
- * Not released the way the per-name families in `store-helper` are, and it does
- * not need to be for the same reason it is keyed this way: a position is reused
- * where a stable id only ever climbs, so the keys here are bounded by the
- * widest the form has ever been rather than by every row it has ever held.
- * Measured going 1 -> 20 -> 14 -> 20 rows: the released families fall back to
- * 23 and this one stays at 29, its high-water mark. Worth knowing before
- * someone reads the absence of a release as an oversight.
+ * Made by whoever subscribes rather than cached by name, so it goes with the
+ * component that asked: a family kept one per name for the life of the page,
+ * and this one was never released at all -- 110 keys after ten definitions of
+ * ten fields. See `useEntryAtom` for the same move on the records a field
+ * writes into.
  */
-/** What the host says about one field, with the sentinel already read. */
-export type HostEntry = {
-    /** The host names this field. A field it does not name reads `undefined`. */
-    found: boolean;
-    value: unknown;
-};
-export declare function readHostEntry(entry: unknown): HostEntry;
-export declare const hostEntryAtom: import("jotai-family").AtomFamily<string, import("jotai").Atom<unknown>>;
+export declare function hostEntryAtom(name: string): import("jotai").Atom<unknown>;

package/dist/types/luna-react/src/client/lib/list-store.d.ts

@@ -1,7 +1,6 @@
 export declare const pendingListRowsAtom: import("jotai").PrimitiveAtom<Record<string, Record<string, unknown>[]>> & {
     init: Record<string, Record<string, unknown>[]>;
 };
-export declare const reportPendingListRowsAtom: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<Record<string, unknown>[] | undefined, [newValue: Record<string, unknown>[] | undefined], void>>;
 /**
  * What a list on screen is holding: the stable ids of its live rows, in the
  * order they are shown, and the name of every leaf a row owns.
@@ -37,4 +36,3 @@ export type MountedList = {
 export declare const mountedListsAtom: import("jotai").PrimitiveAtom<Record<string, MountedList>> & {
     init: Record<string, MountedList>;
 };
-export declare const reportMountedListAtom: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<MountedList | undefined, [newValue: MountedList | undefined], void>>;

package/dist/types/luna-react/src/client/lib/resolve-value.d.ts

@@ -1,6 +1 @@
-export type Entry = {
-    found: boolean;
-    value: unknown;
-};
-export declare function resolveEntry(name: string, currentValue: Record<string, unknown> | unknown[]): Entry;
 export declare function resolveValue(name: string, currentValue: Record<string, unknown> | unknown[]): unknown;

package/dist/types/luna-react/src/client/lib/source-store.d.ts

@@ -1,8 +1,11 @@
 import { type DataSource } from '../../../../luna-core/index';
-export declare const reportSourceAtom: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<DataSource | undefined, [target: string, value: DataSource | undefined], void>>;
-export declare const clearInputSourceAtom: import("jotai").WritableAtom<null, [contributorNames: string[]], void> & {
-    init: null;
+export declare const sourceAtom: import("jotai").PrimitiveAtom<Record<string, Record<string, DataSource>>> & {
+    init: Record<string, Record<string, DataSource>>;
 };
-export declare const releaseInputSourceAtom: import("jotai").WritableAtom<null, [names: string[]], void> & {
+export declare const SOURCE_OPTIONS: {
+    readonly merge: (values: DataSource[]) => DataSource | undefined;
+    readonly validateTarget: (target: string) => boolean;
+};
+export declare const clearInputSourceAtom: import("jotai").WritableAtom<null, [contributorNames: string[]], void> & {
     init: null;
 };

package/dist/types/luna-react/src/client/lib/state-store.d.ts

@@ -2,7 +2,3 @@ import type { FieldState } from '../../../../luna-core/index';
 export declare const fieldStateAtom: import("jotai").PrimitiveAtom<Record<string, FieldState>> & {
     init: Record<string, FieldState>;
 };
-export declare const releaseFieldStateAtom: import("jotai").WritableAtom<null, [names: string[]], void> & {
-    init: null;
-};
-export declare const reportFieldStateAtom: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<FieldState | undefined, [newValue: FieldState | undefined], void>>;

package/dist/types/luna-react/src/client/lib/store-helper.d.ts

@@ -1,15 +1,10 @@
 import { type PrimitiveAtom } from 'jotai';
-type NestedAtomFamilyOptions<TInner> = {
-    merge?: (values: TInner[]) => TInner | undefined;
-    validateTarget?: (target: string) => boolean;
-};
 export declare function omitKey<T extends Record<string, unknown>>(obj: T, key: string): T;
-export declare function createNestedRecordAtomFamily<TInner, TRecord extends Record<string, Record<string, TInner>> = Record<string, Record<string, TInner>>>(baseAtom: PrimitiveAtom<TRecord>, options?: NestedAtomFamilyOptions<TInner>): import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<TInner | undefined, [target: string, value: TInner | undefined], void>>;
-export declare function createNestedReleaseAtom(family: {
-    remove: (name: string) => void;
-}): import("jotai").WritableAtom<null, [names: string[]], void> & {
-    init: null;
-};
+export declare function createEntryAtom<T>(base: PrimitiveAtom<Record<string, T>>, name: string): import("jotai").WritableAtom<NonNullable<T> | undefined, [next: T | undefined], void>;
+export declare function createContributionAtom<T>(base: PrimitiveAtom<Record<string, Record<string, T>>>, name: string, options: Readonly<{
+    merge: (values: T[]) => T | undefined;
+    validateTarget: (target: string) => boolean;
+}>): import("jotai").WritableAtom<T | undefined, [target: string, value: T | undefined], void>;
 export declare function createNestedClearAtom<TInner>(baseAtom: PrimitiveAtom<Record<string, Record<string, TInner>>>): import("jotai").WritableAtom<null, [contributorNames: string[]], void> & {
     init: null;
 };
@@ -26,9 +21,4 @@ export declare function createAtomStore<T>(initialValue?: Record<string, T>): {
     bulkReport: import("jotai").WritableAtom<null, [newValue: Record<string, T>], void> & {
         init: null;
     };
-    release: import("jotai").WritableAtom<null, [names: string[]], void> & {
-        init: null;
-    };
-    report: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<NonNullable<T> | undefined, [newValue: T | undefined], void>>;
 };
-export {};

package/dist/types/luna-react/src/client/lib/value-store.d.ts

@@ -7,10 +7,6 @@ export declare const clearAllValueAtom: import("jotai").WritableAtom<null, [], v
 export declare const clearInputValueAtom: import("jotai").WritableAtom<null, [names: string[]], void> & {
     init: null;
 };
-export declare const releaseInputValueAtom: import("jotai").WritableAtom<null, [names: string[]], void> & {
-    init: null;
-};
-export declare const reportValueAtom: import("jotai-family").AtomFamily<string, import("jotai").WritableAtom<{} | undefined, [newValue: unknown], void>>;
 export declare const appliedAutoFillAtom: import("jotai").PrimitiveAtom<Record<string, unknown>> & {
     init: Record<string, unknown>;
 };

package/dist/types/luna-react/src/component/column.d.ts

@@ -1,3 +1,4 @@
+import { type DescriptionTextProps } from './description';
 import { type Column } from '../../../luna-core/index';
 import type { Config } from '../type';
 export declare function Column(props: Readonly<{
@@ -5,5 +6,6 @@ export declare function Column(props: Readonly<{
     column?: Column;
     config?: Config;
     context?: Record<string, unknown>;
+    description?: React.ComponentType<DescriptionTextProps>;
     translations?: Record<string, string>;
 }>): import("react").JSX.Element;

package/dist/types/luna-react/src/component/description.d.ts

@@ -1,4 +1,13 @@
+import { type Description as DescriptionType } from '../../../luna-core/index';
+import type { Config } from '../type';
 export declare function Description(props: Readonly<{
     children: string | React.ReactNode;
     title?: string;
 }>): import("react").JSX.Element;
+export type DescriptionTextProps = Readonly<{
+    config?: Config;
+    context?: Record<string, unknown>;
+    text?: DescriptionType;
+    translations?: Record<string, string>;
+}>;
+export declare function DescriptionText(props: DescriptionTextProps): import("react").JSX.Element | null;

package/dist/types/luna-react/src/component/field/{field-set.d.ts → field-set-static.d.ts}

@@ -1,5 +1,5 @@
 import { type Section, type Style } from '../../../../luna-core/index';
-export declare function FieldSet(props: Readonly<{
+export declare function StaticFieldSet(props: Readonly<{
     advanced?: {
         step?: boolean;
     };

package/dist/types/luna-react/src/component/field/field.d.ts

@@ -3,7 +3,7 @@ import type { Children } from '../../type';
 export type FieldProps = Readonly<{
     children: Children;
     disabled?: boolean;
-    errors?: Record<string, string[]>;
+    errors?: string[];
     field: Field;
     lang?: string;
     style?: Style;

package/dist/types/luna-react/src/component/field-description.d.ts

@@ -1,8 +1,9 @@
 import type { Config } from '../type';
 import type { Field } from '../../../luna-core/index';
-export declare function FieldDescription(props: Readonly<{
+export type DescriptionProps = Readonly<{
     config?: Config;
     context?: Record<string, unknown>;
     field: Field;
     translations?: Record<string, string>;
-}>): import("react").JSX.Element;
+}>;
+export declare function StaticDescription(props: DescriptionProps): import("react").JSX.Element;

package/dist/types/luna-react/src/component/form.d.ts

@@ -1,6 +1,13 @@
+import { StaticFieldSet } from './field/field-set-static';
 import { type Definition, type Sections } from '../../../luna-core/index';
 import type { Config, Control, Slot } from '../type';
+import type { Fields } from '../../../luna-core/index';
 import type { FormEvent } from 'react';
+export type GuardProps = Readonly<{
+    children: React.ReactNode;
+    fields: Fields;
+}>;
+export declare function StaticGuard(props: GuardProps): import("react").ReactNode;
 export declare function Form(props: Readonly<{
     advanced?: {
         step?: boolean;
@@ -10,6 +17,8 @@ export declare function Form(props: Readonly<{
     config: Config;
     control?: Control;
     definition?: Definition;
+    fieldSet?: React.ComponentType<React.ComponentProps<typeof StaticFieldSet>>;
+    guard?: React.ComponentType<GuardProps>;
     isPending?: boolean;
     noValidate?: boolean;
     onSubmit?: (event: FormEvent<HTMLFormElement>) => void;

package/dist/types/luna-react/src/component/input-group.d.ts

@@ -1,9 +1,11 @@
+import { type DescriptionProps } from './field-description';
 import type { Config } from '../type';
 import type { Field } from '../../../luna-core/index';
 export declare function InputGroup(props: Readonly<{
     children: React.ReactNode;
     config?: Config;
     context?: Record<string, unknown>;
+    description?: React.ComponentType<DescriptionProps>;
     field: Field;
     horizontal?: boolean;
     translations?: Record<string, string>;

package/dist/types/luna-react/src/component/input-label.d.ts

@@ -1,8 +1,10 @@
+import { type DescriptionProps } from './field-description';
 import { type Field } from '../../../luna-core/index';
 import type { Config } from '../type';
 export declare function InputLabel(props: Readonly<{
     config?: Config;
     context?: Record<string, unknown>;
+    description?: React.ComponentType<DescriptionProps>;
     field: Field;
     horizontal?: boolean;
     translations?: Record<string, string>;

package/dist/types/luna-react/src/component/slot/slot-base.d.ts

@@ -1,8 +1,10 @@
 import { type Fields, type Nullable, type Style } from '../../../../luna-core/index';
+import type { DescriptionTextProps } from '../description';
 import type { Children, Config } from '../../type';
 import type { FieldProps } from '../field/field';
 import type { ListProps } from '../field/field-list';
 export type SlotComponents = {
+    description?: React.ComponentType<DescriptionTextProps>;
     field: React.ComponentType<FieldProps>;
     list: React.ComponentType<ListProps>;
 };

package/dist/types/luna-react/src/lib/visibility.d.ts

@@ -0,0 +1,3 @@
+import type { Field, FieldState, Fields, List } from '../../../luna-core/index';
+export declare function isEntryHidden(entry: Fields[number], states: Record<string, FieldState>): boolean;
+export declare function isGuardHidden(states: Record<string, FieldState>, fields: Fields, container?: Field | List): boolean;

package/dist/types/luna-react/src/server/component/field.d.ts

@@ -0,0 +1,2 @@
+import type { FieldProps } from '../../component/field/field';
+export declare function Field(props: FieldProps): import("react").JSX.Element;

package/dist/types/luna-react/src/server/component/list-slot.d.ts

@@ -0,0 +1,2 @@
+import type { ListProps } from '../../component/field/field-list';
+export declare function ListSlot(props: ListProps): import("react").JSX.Element;

package/dist/types/luna-react/src/server/component/slot.d.ts

@@ -0,0 +1,15 @@
+export declare const Slot: (props: Readonly<{
+    children: import("../../type").Children;
+    config: import("../../type").Config;
+    context?: Record<string, unknown>;
+    disabled?: boolean;
+    fields?: import('../../../../luna-core/index').Fields;
+    lang?: string;
+    onValueChange?: (input: {
+        name: string;
+        value: unknown;
+    }) => void;
+    style?: import('../../../../luna-core/index').Style;
+    translations?: Record<string, string>;
+    value?: import('../../../../luna-core/index').Nullable<Record<string, unknown>>;
+}>) => import("react").JSX.Element;

package/docs/forms/submit.md

@@ -113,13 +113,14 @@ it, or put it back, while the errors are showing.
 
 ## Turning submit validation off
 
-`defineConfig({ validation: { submit: false, ... } })` skips the parse
-entirely. The action is called with the raw `FormData` and the schema, and
-nothing is checked, reported or cleared on the way — for a form whose action
-does its own parsing. With no action at all, submitting does nothing.
-
-Remember that this object [replaces the defaults rather than merging](../setup.md#validation),
-so pass the keys you still want.
+`defineConfig({ validation: { submit: false } })` skips the parse entirely. The
+action is called with the raw `FormData` and the schema, and nothing is checked,
+reported or cleared on the way — for a form whose action does its own parsing.
+With no action at all, submitting does nothing.
+
+The other three keys are untouched by that: this object
+[merges into the defaults](../setup.md#validation), so a form that stops
+validating on submit goes on validating as the user types.
 
 ## The error summary
 

package/docs/setup.md

@@ -13,15 +13,15 @@ pnpm add react-luna-form
 The package carries no dependencies of its own: everything it needs is a peer
 dependency, so your application resolves one copy of React, Zod and the rest.
 
-| Peer                    | Version             | Used for                                    |
-| ----------------------- | ------------------- | ------------------------------------------- |
-| `react`, `react-dom`    | `^19.0.0`           | rendering, and `useActionState` on submit   |
-| `zod`                   | `^4.0.0`            | the schema derived from `sections`          |
-| `jotai`, `jotai-family` | `^2.0.0` / `^1.0.0` | the value, error and source stores          |
-| `swr`                   | `^2.0.0`            | fetching a field's remote `source`          |
-| `date-fns`              | `^4.0.0`            | date and time formatting, `duration` filter |
-| `fast-equals`           | `^6.0.0`            | change detection in the stores              |
-| `tailwind-merge`        | `^3.5.0`            | merging the classes the components render   |
+| Peer                 | Version   | Used for                                    |
+| -------------------- | --------- | ------------------------------------------- |
+| `react`, `react-dom` | `^19.0.0` | rendering, and `useActionState` on submit   |
+| `zod`                | `^4.0.0`  | the schema derived from `sections`          |
+| `jotai`              | `^2.0.0`  | the value, error and source stores          |
+| `swr`                | `^2.0.0`  | fetching a field's remote `source`          |
+| `date-fns`           | `^4.0.0`  | date and time formatting, `duration` filter |
+| `fast-equals`        | `^6.0.0`  | change detection in the stores              |
+| `tailwind-merge`     | `^3.7.0`  | merging the classes the components render   |
 
 None of them is optional, and none is bundled. A package manager that installs
 peers automatically (npm 7+, or pnpm with `auto-install-peers=true`) brings
@@ -48,20 +48,26 @@ CSS.
 
 Every element also carries a `data-slot` attribute — `field`, `field-label`,
 `field-control`, `field-set`, `field-set-content`, `field-content`,
-`field-group`, `field-separator`, `column`, `list-item-card` — so a design
-system can restyle the structure without patching the library. The components
-you register yourself are yours to style; these slots cover the scaffolding
-around them.
+`field-group`, `field-separator`, `collapsible-content`, `column`,
+`list-item-card` — so a design system can restyle the structure without
+patching the library. The components you register yourself are yours to style;
+these slots cover the scaffolding around them.
 
 ## Entry points
 
 | Import                   | Contains                                                                                  |
 | ------------------------ | ----------------------------------------------------------------------------------------- |
 | `react-luna-form`        | `Form` (client), `withDeclaredFields`, and the `Sections`, `Source` and `ZodSchema` types |
-| `react-luna-form/server` | `Form` (server) and `Fallback`                                                            |
+| `react-luna-form/server` | `Form` (server) and `Fallback`, usable under the `react-server` condition                 |
 | `react-luna-form/config` | `defineConfig` and the `define*` registration helpers                                     |
 | `react-luna-form/schema` | `buildFormSchema` and `collectIssues`                                                     |
 
+The client bundle is published carrying a `'use client'` directive, so an App
+Router project imports `Form` straight from a Server Component and needs no
+wrapper module of its own to say it. The server bundle carries none and
+resolves under the `react-server` condition, which is what lets a Server
+Component render the form itself.
+
 ## Configuring
 
 `defineConfig` is called once, usually in a `luna.config.ts` at the root of the
@@ -99,10 +105,9 @@ When to validate and whether to summarise errors. All four default to `true`.
 validation: { blur: true, change: true, showError: true, submit: true }
 ```
 
-**This object replaces the defaults, it does not merge into them.** Passing
-`{ change: false }` also turns off `blur`, `submit` and `showError`, so the form
-stops validating on blur and loses its error summary with no indication why.
-Pass every key you still want.
+This object merges into the defaults, so pass only what you want to change.
+`{ change: false }` stops the form validating as the user types and leaves the
+other three alone.
 
 ### `fetcher.remotePatterns`
 
@@ -127,7 +132,8 @@ fetcher: {
 A blocked URL is not an error. The library logs
 `URL blocked by remotePatterns: <url>` and the field renders with no options at
 all, which on screen looks like an empty select rather than a rejected request.
-Check the console when a remote source comes back empty.
+Check the console when a remote source comes back empty — see
+[Warnings](#warnings) for when that line is written.
 
 ### `style`, `alert`, `env`
 
@@ -137,6 +143,20 @@ Check the console when a remote source comes back empty.
 - `env` is a flat record of values available to interpolation, in labels and in
   descriptions. Its `locale` key is also what those two read to format values.
 
+## Warnings
+
+Some of what can go wrong is nobody's to fix but the author of the form, and
+the library says so on the console rather than on screen: a `pattern` that does
+not compile, a field name that reaches a prototype and is left out of the
+submit, the error an `action` threw, a remote `source` that failed or was
+blocked. Every one of those lines is prefixed `[Luna Form]`.
+
+They are written outside production and silent inside it, and which one you are
+in is your build's answer to give: the published bundle leaves
+`process.env.NODE_ENV` for your bundler to resolve instead of deciding while it
+is being packaged. A development build of your application shows them and a
+production build does not. Where nothing defines it at all, they are shown.
+
 ## Rendering
 
 ### `Form` from `react-luna-form`

package/docs/validation/overview.md

@@ -111,7 +111,7 @@ Validates a string value against a regular expression.
 
 `pattern` never fires on an empty value — pair it with `required`/`requiredWhen` when the field is mandatory.
 
-A `regex` or `flags` that does not compile is a mistake in the definition, not in the value. The rule then holds back every value it checks with its `message`, as it does a value that does not match, and the form keeps working. The same goes for a `pattern` among [`rules`](#rules).
+A `regex` or `flags` that does not compile is a mistake in the definition, not in the value. The rule then holds back every value it checks with its `message`, as it does a value that does not match, and the form keeps working. The same goes for a `pattern` among [`rules`](#rules). Since the `message` is written for whoever fills the form in, the expression that failed to compile is named on the console instead — see [Warnings](../setup.md#warnings).
 
 A `regex` that compiles runs as written, on what the user types: in the browser when the form is submitted, and on the server when it validates with `buildFormSchema`. Nothing inspects it first, so it is part of the code the form ships with. Accept one only from someone you would let write that code.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-luna-form",
-  "version": "0.0.86",
+  "version": "0.0.87",
   "description": "A React library for building forms based on JSON",
   "main": "./dist/client/cjs/index.js",
   "module": "./dist/client/esm/index.js",
@@ -22,20 +22,20 @@
     "date-fns": "^4.0.0",
     "fast-equals": "^6.0.0",
     "jotai": "^2.0.0",
-    "jotai-family": "^1.0.0",
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
     "swr": "^2.0.0",
-    "tailwind-merge": "^3.5.0",
+    "tailwind-merge": "^3.7.0",
     "zod": "^4.0.0"
   },
   "devDependencies": {
-    "@luna-form/core": "0.0.86",
+    "@luna-form/core": "0.0.87",
     "@types/react": "19.3.0",
     "@types/react-dom": "19.3.0",
     "eslint-plugin-react": "7.37.5",
     "eslint-plugin-react-hooks": "7.1.1",
-    "eslint-plugin-react-refresh": "0.5.7"
+    "eslint-plugin-react-refresh": "0.5.7",
+    "jotai-family": "1.1.0"
   },
   "license": "Apache-2.0",
   "repository": {

package/dist/types/luna-react/src/client/component/field/field-with-state.d.ts

@@ -1,13 +0,0 @@
-export declare function withError<P extends {
-    errors?: Record<string, string[]>;
-    field: {
-        name: string;
-    };
-}>(Component: React.ComponentType<P>): (props: Readonly<P>) => import("react").JSX.Element | null;
-export declare function withState<P extends {
-    disabled?: boolean;
-    field: {
-        name: string;
-        hidden?: boolean;
-    };
-}>(Component: React.ComponentType<P>): (props: Readonly<P>) => import("react").JSX.Element | null;