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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@reformer/core

v10.2.0

Published

Reactive form state management library for React with signals-based architecture

Readme

@reformer/core

npm version npm downloads License: MIT

Reactive form state management library for React with signals-based architecture.

Playground

Open in StackBlitz

Documentation

Full documentation is available at https://alexandrbukhtatyy.github.io/ReFormer/

Features

  • Signals-based reactive state management
  • Declarative form validation
  • Dynamic form behaviors
  • TypeScript support
  • Tree-shakeable exports

Installation

npm install @reformer/core@beta # Active development is underway, so you can try beta

Quick Start

ReFormer is built around the M1 architecture: a reactive FormModel owns the values, a layout schema binds field config (component / props) to the model's signals, and createForm({ model, schema }) wires them into a typed form. Validation is a separate ambient contract — defineValidationSchema, run on demand by validateModel(model, schema) — so the layout schema carries no validators.

import { useMemo } from 'react';
import {
  createModel,
  createForm,
  useFormControl,
  type FieldNode,
  type ValidationError,
} from '@reformer/core';
import { validate, cross, defineValidationSchema, validateModel } from '@reformer/core/validation';
import { required, email, minLength } from '@reformer/core/validators';
import { defineFormBehavior, onChange } from '@reformer/core/behaviors';

// 0. Simple FormField component
function FormField({ label, control }: { label: string; control: FieldNode<string> }) {
  const { value, errors, shouldShowError } = useFormControl(control);

  return (
    <div>
      <label>{label}</label>
      <input
        value={value ?? ''}
        onChange={(e) => control.setValue(e.target.value)}
        onBlur={() => control.markAsTouched()}
      />
      {shouldShowError && <span className="error">{errors[0].message}</span>}
    </div>
  );
}

// 1. Define form interface
interface RegistrationForm {
  username: string;
  email: string;
  password: string;
  confirmPassword: string;
}

// 2. Reactive model — the source of truth for values
const model = createModel<RegistrationForm>({
  username: '',
  email: '',
  password: '',
  confirmPassword: '',
});

// 3. Layout schema — binds field config (component / props) to model signals
//    (`model.$.<field>`). Layout carries NO validators; rules live in the
//    validation schema below.
const schema = {
  children: [
    { value: model.$.username, component: Input },
    { value: model.$.email, component: Input },
    { value: model.$.password, component: Input },
    { value: model.$.confirmPassword, component: Input },
  ],
};

// 4. Validation schema — a separate ambient contract from `@reformer/core/validation`,
//    run on demand (not reactive). Field rules go through `validate(sig, [rules])`;
//    cross-field rules through `cross(sig, snapshot => error | null)` where the snapshot
//    is `model.get()`. Rule factories (`required()`/…) come from `@reformer/core/validators`.
const passwordsMatch = (f: RegistrationForm): ValidationError | null =>
  f.confirmPassword && f.password && f.confirmPassword !== f.password
    ? { code: 'mismatch', message: 'Passwords do not match' }
    : null;

const validationSchema = defineValidationSchema<RegistrationForm>(({ model }) => {
  validate(model.$.username, [required(), minLength(2)]);
  validate(model.$.email, [required(), email()]);
  validate(model.$.password, [required(), minLength(8)]);
  validate(model.$.confirmPassword, [required()]);
  cross(model.$.confirmPassword, passwordsMatch);
});

// 5. Behavior — declarative reactive logic, run by `createForm({ behavior })`.
//    Validation runs on demand, so the stale cross-field error on `confirmPassword`
//    is cleared the moment `password` changes — a behavior→validation bridge.
const behavior = defineFormBehavior<RegistrationForm>(({ model, form }) => {
  onChange(model.$.password, () => {
    form.confirmPassword.clearErrors();
  });
});

// 6. Registration form component
function RegistrationFormExample() {
  const form = useMemo(() => createForm<RegistrationForm>({ model, schema, behavior }), []);

  const handleSubmit = async (e: React.FormEvent) => {
    e.preventDefault();
    form.touchAll();
    // Validate the whole model against the validation schema (sync + async) on demand;
    // errors route into the form nodes, so the UI highlights the offending fields.
    const valid = await validateModel(model, validationSchema);
    if (valid) {
      console.log('Form data:', model.get());
    }
  };

  return (
    <form onSubmit={handleSubmit}>
      <FormField label="Username" control={form.username} />
      <FormField label="Email" control={form.email} />
      <FormField label="Password" control={form.password} />
      <FormField label="Confirm Password" control={form.confirmPassword} />
      <button type="submit">Register</button>
    </form>
  );
}

License

MIT