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

@open-form-build/core

v0.3.0

Published

Forms your agent writes. Responses you own. An open-source form framework for coding agents: your agent writes the questions and logic, and Open Form handles the runtime, validation, submissions, storage and responses.

Readme

@open-form-build/core

Forms your agent writes. Responses you own. Open Form is an open-source form framework for coding agents: your agent writes the questions and logic, and Open Form provides the runtime, validation, responsive UI, submission API, spam protection, SQLite storage and a Responses Studio.

pnpm create open-form my-forms
cd my-forms
pnpm dev

npm create open-form@latest my-forms works too; then it's npm run dev. Init prints the commands for the package manager you ran it with. The CLI is open-form.

// forms/meetup/index.tsx
import { defineForm, Email, Form, Page, Select, Submit, Text, When } from '@open-form-build/core';

export const config = defineForm({
  title: 'Developer Meetup',
  submissions: { maxResponses: 100, uniqueBy: 'email' },
});

export default function Meetup() {
  return (
    <Form>
      <Page title="About you">
        <Text name="name" label="Name" required />
        <Email name="email" label="Email" required />
      </Page>
      <Page title="Background">
        <Select name="role" label="Role" options={['Student', 'Engineer', 'Designer']} />
        <When field="role" equals="Student">
          <Text name="school" label="School" required />
        </When>
      </Page>
      <Submit>Register</Submit>
    </Form>
  );
}

Entry points

| Import | What | | --- | --- | | @open-form-build/core | DSL for forms: Form, Page, When, fields, useField, defineForm, defineTheme, defineConfig | | @open-form-build/core/schema | Framework-agnostic schema, conditions and validation | | @open-form-build/core/server | Web-standard (Request) => Response handler and storage interface | | @open-form-build/core/sqlite | node:sqlite storage adapter | | @open-form-build/core/node | Node HTTP adapter and production server | | @open-form-build/core/vite | The Vite config and project helpers the CLI is built on (createViteConfig, findForms, loadUserConfig) | | @open-form-build/core/next | Next.js route handlers (createOpenFormRoute) | | @open-form-build/core/styles.css | Runtime styles (when rendering forms in your own React app with <FormHost>) | | @open-form-build/core/env | Types for images and CSS imported from forms (*.svg, *.png, *.css, …); the workspace tsconfig.json loads it with "types": ["@open-form-build/core/env"] |

Next.js

Install @open-form-build/core and keep forms/ (and optionally open-form.config.ts) at the root of your Next.js app; a form's look travels with it in forms/<id>/theme/. Then mount the API and render forms with <FormHost>:

// app/api/[...openform]/route.ts
import { createOpenFormRoute } from '@open-form-build/core/next';

export const { GET, POST, PUT, DELETE, OPTIONS } = createOpenFormRoute();

Don't add export const dynamic to the route: Next.js 16 rejects it when Cache Components is on, the default in new apps.

// app/rsvp/rsvp-form.tsx
'use client';
import { FormHost } from '@open-form-build/core';
import '@open-form-build/core/styles.css';
import Rsvp, { config } from '../../forms/rsvp';

export function RsvpForm() {
  return <FormHost id="rsvp" form={Rsvp} config={config} />;
}
{
  "scripts": {
    "dev": "open-form build --server-only --watch & next dev",
    "build": "open-form build --server-only && next build"
  }
}

On Windows cmd, & doesn't run the two in parallel; run open-form build --server-only --watch and next dev in two terminals instead.

App Router route handlers can't render the forms to learn their fields, so the route reads the server bundle open-form build --server-only writes to dist/server/entry.js (outside production it reloads it after each rebuild) — validation still comes from the same form files as the browser. Next.js can't trace that file, so with output: 'standalone' or on Vercel add outputFileTracingIncludes: { '/api/*': ['./dist/server/**/*'] } to next.config, and set OPEN_FORM_SECRET, since serverless functions can't write the secret file generated next to the database. Responses go to SQLite in .open-form/ by default, which needs a persistent disk; pass storage for anything else. The admin API exists only when OPEN_FORM_ADMIN_PASSWORD is set or you pass adminAuth (for example authorize: async () => isAdmin(await auth())). On Vercel, pass waitUntil: after (from next/server) so webhooks finish after the response.

CLI

open-form init | dev | build [--server-only] [--watch] | start | create <id> [--theme] | delete <id> | list | check [id] | comments [id] | responses export <id> | theme list|check|add|font | sync:skills

Every command except init loads .env from the current folder when there is one; variables already set in the environment win.

Requires Node.js 22.13+.

MIT