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

@kamod-ch/otok-validation

v2.0.0

Published

Standard Schema validation for Otok — typed inputs, field errors, and defineAction integration.

Readme

@kamod-ch/otok-validation

Standard Schema validation for Otok — typed inputs, field/form errors, and defineAction integration. Works with Zod, Valibot, and ArkType without forcing a schema library in Otok core.

defineAction with schema

import { defineAction } from "@kamod-ch/otok-validation/loader";
import { contactSchema } from "./schemas/contact";

export const action = defineAction({
  schema: contactSchema,
  handler: async ({ input, db }) => {
    return db.insertInto("contacts").values(input).executeTakeFirstOrThrow();
  },
});

Input is automatically parsed from FormData (HTML forms) or JSON (Content-Type: application/json).

Manual parsing

import { parseFormData, parseJson, parseParams } from "@kamod-ch/otok-validation";

const input = await parseFormData(formData, contactSchema);
const body = await parseJson(request, contactSchema);
const { id } = await parseParams(params, z.object({ id: z.coerce.number() }));

Error format

All parsers throw Otok validationError() with a consistent shape:

{
  status: 400,
  message: "Validation failed",
  fieldErrors: { email: ["Invalid email address"] },
  formErrors?: ["Root-level error"],
  values?: { email: "bad", name: "Ada" }  // safe redisplay values
}

Use actionData.fieldErrors and actionData.values in your page component for progressive enhancement.

Schema libraries

All libraries implementing Standard Schema V1 work natively:

| Library | Import | |----------|--------| | Zod 4+ | Pass schema directly | | Valibot | @kamod-ch/otok-validation/adapters/valibot | | ArkType | @kamod-ch/otok-validation/adapters/arktype |

Legacy Zod 3 safeParse schemas are also supported.

Client-side validation

Same contract on server and client — no schema library in Otok core:

import { safeValidate } from "@kamod-ch/otok-validation/client";

const result = await safeValidate(contactSchema, formValues);
if (!result.success) {
  showErrors(result.fieldErrors);
}

Unknown fields

Pass stripUnknown: true in parse options to remove fields not defined in your schema before validation.