Repository navigation
Releases: wmzy/react-f0rm
Releases · wmzy/react-f0rm
Release list
v1.5.0
v1.4.0
1.4.0 (2026-09-10)
Features
- form.register binding, useField inputProps, disabled subtree propagation, errors tree, and validateMode (26df560)
- framework-free array movers, useErrors record, and OpaqueTypes path registry (ae918cd)
- framework-free watch, Standard Schema direct support and CI/bench tooling (fda5803)
- node10 redirect stubs, dual .d.mts/.d.cts exports, valuesFromFormData, and devtools events tab (e625ebb)
- shouldUseNativeValidation, typed FieldErrors, useStore selector, and devtools submit traces (49f8b6c)
v1.3.0
1.3.0 (2026-09-09)
Features
- add useTransform, useIsFieldDirty, and per-field isDirty/validating (1ba5ce0)
- add validateOnMount, status, valueAsNumber/valueAsDate, and un-vendor the emitter (c058961)
- asyncAlways validation, rules.validate callbacks, native constraint attrs (8b37fcc)
- zero runtime dependencies and RHF/TanStack parity options (87c1438)
v1.2.0
v1.1.1
v1.1.0
1.1.0 (2026-09-03)
Bug Fixes
- attach the full error list to ensureValidate's rejection error (a521f60)
- generate useFieldArray row ids from a per-form counter (a0c0992)
- removeField emits path-scoped events instead of waking every subscriber (a0940bf)
- reset keepDirtyValues snapshots structured segments, not dotted strings (4c3982e)
- seed useField initialValue during render so the first paint and SSR carry it (c5a3f26)
- trigger(name) waits only the triggered fields' validation to settle (48fb212)
- warn in DEV when two fields compete for one changeHandler slot (a234f91)
Features
- field-level validateDeps on useField — re-run a field's validator when its dependencies change (e590c23)
Performance Improvements
- memoize getValues per form through a version-bumped cache (ddf3dd2)
v1.0.0
1.0.0 (2026-09-02)
- feat!: reject dotted numeric path segments (2fb54db)
BREAKING CHANGES
- dotted numeric path segments now throw a TypeError.
Replace 'items.0.name' with 'items[0].name' (or the segment array
['items', 0, 'name']); quoted 'items["0"]' keeps addressing an explicit
string key. getErrors/getDirtyFields/getTouchedFields output paths stay
dotted display strings and are unaffected.