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

@zap-studio/validation

v0.2.1

Published

Standard Schema utilities and ValidationError helpers.

Readme

@zap-studio/validation

Standard Schema utilities and helpers.

Why @zap-studio/validation?

When you validate data with different Standard Schema-compatible libraries (Zod, Valibot, ArkType, etc.), it is easy to end up with slightly different patterns for checking schemas and handling validation errors.

@zap-studio/validation provides a small, focused set of helpers that give you:

  • A single ValidationError type to represent schema validation failures.
  • A type-safe isStandardSchema guard to detect Standard Schema-compatible schemas.
  • A standardValidate helper that normalizes sync/async validation and error handling.
  • A createSyncStandardValidator helper for building synchronous validators from Standard Schema schemas.

Installation

pnpm add @zap-studio/validation
# or
npm install @zap-studio/validation

Quick Start

import { z } from "zod";
import {
  createSyncStandardValidator,
  isStandardSchema,
  standardValidate,
} from "@zap-studio/validation";
import { ValidationError } from "@zap-studio/validation/errors";

const UserSchema = z.object({
  id: z.number(),
  email: z.string().email(),
});

// Type guard for Standard Schema-compatible schemas
if (!isStandardSchema(UserSchema)) {
  throw new Error("Schema is not Standard Schema-compatible");
}

// Create a sync-only validator (throws if schema is async)
const validateUser = createSyncStandardValidator(UserSchema);
const syncResult = validateUser(data);
if (syncResult.issues) {
  console.error("Sync validation failed:", syncResult.issues);
}

try {
  // Throwing mode
  const user = await standardValidate(UserSchema, data, true);
  console.log(user.email);
} catch (error) {
  if (error instanceof ValidationError) {
    console.error("Validation failed:", error.issues);
  }
}

// Non-throwing mode
const result = await standardValidate(UserSchema, data, false);
if (result.issues) {
  console.error("Validation failed:", result.issues);
} else {
  console.log("Validation passed:", result.value);
}