Reducer Form

@nimibyte/reducer-form - Reducer-driven form state primitives for explicit transitions and predictable validation.

ReactNext.jsTypeScript

Design Intent

Avoids repeated ad-hoc form state handling across complex product flows.

Form behavior drifts when field updates, validation, and derived values are scattered across local handlers. Control becomes implicit and difficult to reason about.

Trade-offs: Prioritizes explicit reducer transitions over highly abstract, magic-driven APIs.

Intentionally not solving: Schema engines, UI form builders, or opinionated component rendering layers.

API Surface

Setup

useForm<T>(options)
FormProvider
useFormContext<T>()

Field API

register({ name, required?, type? })
set(name, value)
reset()

State

state
errors
loading

Actions

onSubmit

Use It When

Forms include dependent fields, derived values, or non-trivial transitions.
You need deterministic submit and validation behavior across screens.
You want form state logic decoupled from presentational components.

Avoid It When

The form is a simple input capture flow with minimal branching.
You require a full schema orchestration framework out of the box.
Your stack depends on implicit abstractions over explicit transitions.

Engineering Signal

This reflects Nimibyte's engineering posture: narrow control surfaces, explicit state transitions, and predictable runtime behavior. We prioritize maintainability over convenience abstractions.

Explore our engineering approach ->