mobx-react-form is now mobx-formkit
The mobx-react-form package — after 273 releases ending with 7.1.0 — is now published on npm as mobx-formkit . The old package name is marked as deprecated on the npm registry: anyone installing mobx-react-form today gets a deprecation notice pointing to mobx-formkit , with no breaking change for existing installs already pinned to the old name. The new package is a fresh 1.0.0 release on top of…
The mobx-react-form package, after 273 releases ending with 7.1.0, has been rebranded as mobx-formkit on npm. The old package name is marked as deprecated on the npm registry, and installing the old name leads to a deprecation notice pointing to the new mobx-formkit package with no breaking changes for existing installations that are pinned to the old name.
The new package is a fresh 1.0.0 release built on the same codebase (7.1.0 API) with a name that better represents its capabilities - MobX form state management rather than a React-only project. The GitHub repo, demo app, and documentation all moved along with the rebrand. While the APIs remain identical, the only breaking change is in UMD bundle filenames and script-tag globals that now reflect the new package name instead of MobxReactForm*.
The library is UI-agnostic and works with any reactive consumer, not just React, and supports various UI frameworks like Material UI, Ant Design, React Aria, Headless UI, React Select, React Widgets, Vue 3, Lit, Angular, Solid, Octane, and vanilla JavaScript. The validation drivers have been updated to support VALIBOT and VINEJS, both of which offer additional features and improvements over the previous validation drivers.
The core Form / Field methods remain unchanged, and the library now supports per-field errors for nested and array paths automatically when using VALIBOT. All drivers support the extend callback, and both sync and async validation promises are intact. The migration path is simple: install mobx-formkit, keep mobx-react-form around temporarily, and swap imports to mobx-formkit.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.