npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@mozartspa/mobx-form

v0.7.0

Published

High performance, hook-based forms library for React powered by MobX

Readme

@mozartspa/mobx-react

High performance, hook-based forms library for React, powered by MobX.

Features

  • Form level and Field level validation with built-in async debouncing
  • Supports multiple error messages per field
  • Deeply nested form values (arrays, you're welcome)
  • Format and parse values (to support advanced scenarios)
  • Powered by MobX
  • Built with React hooks
  • Written in Typescript
  • Minzipped Size

Motivation

Why another form library? Simple, I have not found easy to use form libraries that leveraged the high performance of mobx. The mostly used form libraries don't use MobX underneath, and they struggle between performance and ease of use. With MobX you can have both.

Installation

yarn add @mozartspa/mobx-form

Then install the peer-dependencies: mobx and mobx-react-lite

yarn add mobx mobx-react-lite

Links

Quickstart

A minimal example, not exactly what you would use in a real project, but it gives an overall look:

import React from "react"
import { observer } from "mobx-react-lite"
import { useField, useForm } from "@mozartspa/mobx-form"

const App = observer(() => {
  const form = useForm({
    initialValues: {
      name: "",
    },
    onSubmit: (values) => {
      console.log("submitted values", values)
    },
  })

  const nameField = useField("name", { form })

  return (
    <form onSubmit={form.handleSubmit}>
      <div>
        <label>Name</label>
        <input type="text" {...nameField.input} />
        {nameField.isTouched && nameField.error}
      </div>
      <button type="submit">Submit</button>
    </form>
  )
})

export default App

Few things to note:

  • We import useForm and useField from the package @mozartspa/mobx-form.
  • We wrap our component with observer(), since we're using MobX.
  • useForm() gives us back a stable reference to our form instance.
  • useField() gives us back a reference to a specific field of our form. We pass it the form instance, to make it know which form it should be bound to. It's required here, but in other examples we'll leverage the React Context.
  • With onSubmit={form.handleSubmit} we let our form instance handle the onSubmit event.
  • {...nameField.input} gives the input the necessary props to be a controlled input: name, value, onChange, onBlur.
  • With {nameField.isTouched && nameField.error} we display the possible error only after the user touched the input. Anyway, in this case there's no input validation.

Credits

Heavily inspired by formik, with some ideas taken from react-form and react-final-form.