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

@boostkit/validation

v0.0.2

Published

Zod-powered request validation for BoostKit — inline helpers, middleware factories, and class-based form requests.

Readme

@boostkit/validation

Zod-powered request validation for BoostKit — inline helpers, middleware factories, and class-based form requests.

Installation

pnpm add @boostkit/validation

Usage

Inline validation

import { validate, z } from '@boostkit/validation'

const data = await validate(
  z.object({ name: z.string().min(1), age: z.coerce.number().int() }),
  req
)
// data: { name: string; age: number }

Middleware factory

import { validateWith, z } from '@boostkit/validation'

const mw = validateWith(z.object({ email: z.string().email() }))

router.post('/api/users', mw, handler)

validateWith() throws ValidationError on invalid input; it does not mutate req.body.

Class-based form request

import { FormRequest, z } from '@boostkit/validation'

class CreateUserRequest extends FormRequest {
  rules() {
    return z.object({
      name:  z.string().min(2),
      email: z.string().email(),
    })
  }

  override authorize(): boolean {
    return (this.req as any).user?.role === 'admin'
  }
}

// In a route handler:
const data = await new CreateUserRequest().validate(req)

Handling errors

import { validate, ValidationError, z } from '@boostkit/validation'

try {
  const data = await validate(schema, req)
} catch (err) {
  if (err instanceof ValidationError) {
    res.status(422).json(err.toJSON())
    // → { message: 'Validation failed', errors: { email: ['Invalid email'] } }
  }
}

API Reference

validate(schema, req)

Merges req.params, req.query, and req.body (params take priority) and parses against schema. Returns typed data or throws ValidationError.

validateWith(schema)

Returns a MiddlewareHandler that runs validate() and calls next() on success. Does not attach parsed data to req.body.

FormRequest

Abstract base class. Extend and implement rules():

| Method | Signature | Description | |--------|-----------|-------------| | rules() | abstract rules(): ZodType | Define the validation schema | | authorize() | (): boolean | Authorization check (default: true) | | validate(req) | async (req: AppRequest): Promise<z.infer<T>> | Run authorization + validation |

this.req is available inside rules() and authorize() after validate() is called.

ValidationError

| Property | Type | Description | |----------|------|-------------| | name | 'ValidationError' | Error name | | message | 'Validation failed' | Human-readable message | | errors | Record<string, string[]> | Field → error messages map | | toJSON() | () => { message, errors } | Serializable shape |

Nested paths are joined with . (e.g. address.city). Top-level schema errors use 'root'. Auth failures use 'auth'.

z

Re-export of Zod's z namespace — no separate zod import needed.