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

eigenform

v0.1.1

Published

An advanced, high-performance form system built for exensibility and seamless integration

Downloads

3

Readme

eigenform (WIP)

An advanced, high-performance form system built for exensibility and seamless integration into your design systems.

Part of the eigencode project.

npm install eigenform

Features:

  • Nested objects
  • Client-side and server-side validation
  • Conditionally rendered sections
  • Repeated sections

This Readme is currently under construction - check back later, or read on for a taster of the API

Example

import { Form, Field, Label, TextInput, Conditional, Multiple } from 'eigenform';

<Form>
  <Field name="fullName" label="your name">
    <Label>Full name:</Label>
    <TextInput max={30} min={2} />
  </Field>

  <Field name="age" optional label="your age">
    <Label>Your age (optional):</Label>
    <NumberInput />
  </Field>

  <Field name="hasNickname" omit label="you have a nickname">
    <Label>Do you have a nickname?</Label>
    <YesNoInput />
  </Field>

  <Conditional when="hasNickname" is={true}>
    <Field name="nickname" label="your nickname">
      <Label>Your nickname:</Label>
      <TextInput max={30} />
    </Field>
  </Conditional>

  <h3>Which countries are you a citzen of?</h3>
  <Multiple name="countries" min={1} max={5}>
    <Label>Enter a country name ({Multiple.ordinal} of {Multiple.total})</Label>
    <TextInput />
  </Multiple>

  <Button onClick={Form.submit} />
</Form>

Concepts

Forms and Fields

<Fields /> are the fundamental unit of data in your forms: Every <Field /> element corresponds to a value in your data model, and is the entity that can have validation tests against it.

The <Form /> element wraps around your fields to build up your over-all data model, orchestrates top-level validation and provides the means to submit your form.

Inputs

Eigenform provides several controls to be rendered inside your form for data entry. Collectively called Input components, these are located inside <Field /> components to update the value of that field. The Input components available out of the box are:

  • TextInput
  • NumberInput
  • EmailInput
  • Radio
  • Checkbox
  • Select

But of course you can add your own.

Groups

Groups allow you to define nested data structures and instrument sets of <Field />s for re-use.

Conditionals

Fields and options that should only be shown when certain conditions on the form data are met can be controlled with <Conditional /> components.

Multiples

To let the form accept multiple answers for a field or set of fields, wrap them in a <Multiple /> component that will offer users to "Add another" group of answers.

Validation

The props of <Field />s and their contained inputs are used to build up a validation schema that generates feedback messages if validation requirements are not met. You can extend or replace the validation behaviour by setting a validator prop on <Field />, and set the messaging by setting a label on <Field />