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

@formskit/engine

v1.0.0

Published

Headless forms engine. Types, authoring contracts, expression vectors, runtime evaluation, form input sessions, lint, and JSON Schema. Hosts supply a FieldRegistry and their own UI.

Readme

@formskit/engine

Headless forms runtime. Evaluates expressions, drives form input sessions, validates schemas, and produces submission payloads. No UI — hosts render FormState themselves.

Install

import {
  createFormInputSession,
  computeFormState,
  setFieldValue,
  buildSubmission,
  lintSchema,
  evaluateExpr,
  defineRegistry,
  type FormSchema,
} from '@formskit/engine'

Form input session

Every call requires a host registry:

const registry = defineRegistry({ /* ... */ })

const session = createFormInputSession(schema, {
  registry,
  ctx: { user: { role: 'admin' } },
})

const state = computeFormState(session)
// state.fields[id].visible, .required, .errors, .value
// state.canSubmit

session = setFieldValue(session, 'name', 'Ada')
const submission = buildSubmission(session)

buildSubmission strips hidden and non-input fields. Hidden values stay in session.draft until submit.

Lint

Validate a schema against your registry before publish:

const issues = lintSchema(schema, registry)
// unknownFieldType, unknownOptionKey, broken refs, etc.

Package layout (src)

See STRUCTURE.md for the full breakdown and "where does X live?" guide.

Quick summary:

  • expressions/ — grammar, builders (ref/expr), evaluator, vectors (contract tests)
  • registry/FieldRegistry, defineRegistry, opt, contracts, makeStubRegistry, TEST_FIELD_REGISTRY
  • authoring/field*, defineForm*, defineRegistryField*, ordered*
  • runtime/createFormInputSession, computeFormState, etc.
  • traversal/walkFields, computeInnerRefs, lintSchema
  • types/ — core schema + runtime types (split for clarity)
  • fixtures/ — conformance schemas + TUTORIAL_FORM
  • index.ts (full), authoring.ts (subpath barrel)

Expressions

Lower-level exports for custom tooling:

evaluateExpr(expr, { fields, ctx })
evalBool(boolOrExpr, scope)
collectExprRefs(expr)
normalizeExpr(expr)

Semantics are locked by EXPRESSION_VECTORS (exported from this package). Vector tests live alongside the evaluator.

Renderer contract

Read FormState — do not re-implement required, visible, or validation in the UI. Submit via buildSubmission(session).

Server validation

Run the same session API server-side with the same registry and submitted values in draft, then check computeFormState(session).canSubmit.

Docs

Project README · Host integration · Expressions