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

@warblerjs/validators

v0.6.0

Published

Transport-independent strict validation powered by Warbler's native validator engine.

Readme

@warblerjs/validators

Transport-independent strict validation powered by Warbler's native validator engine.

rules is the primary payload for every transport. messageRules is reserved for a distinct message-envelope section; it is never an alias for rules. Transports parse bytes and requests before passing plain values to a compiled validator.

import { compileValidator, v } from "@warblerjs/validators";

const validator = compileValidator({
  rules: { name: v.string("validators.invalid_name") },
});
const result = validator.execute({ value: { name: "Warbler" } });

onValidationError

By default, a request that fails validation short-circuits to Warbler's standard validation-error response (HTTP 400, one translated message per failing field) and the controller never runs. Supplying an optional onValidationError(req, errors) on defineValidator(...) overrides that default: when present, it runs instead, and its returned Response is sent verbatim.

onValidationError defined     → its Response is used
onValidationError not defined → Warbler's default validation-error response is used
  • req is the raw, un-validated request — native, headers, cookies, context, locale, and tr(...) behave exactly as on a successful AppRequest, but body/params/query are intentionally untyped (unknown): the input failed validation, so it is never presented as if it were the validated output.
  • errors is the same structured ValidationErrors map ({ [source.field]: ValidationIssue[] }) produced by compileValidator(...).execute(...) — nothing is translated or reshaped for you.
  • The handler may be synchronous or asynchronous (Response | Promise<Response>).
  • The controller never runs once validation has failed, whether or not a handler is supplied.
  • A throwing/rejecting handler is not caught here — it propagates through Warbler's normal runtime/HTTP error handling, the same as a controller throwing.
import { defineValidator, v } from "@warblerjs/validators";
import { view } from "@warblerjs/view";

export const validateUserId = defineValidator({
  paramRules: {
    id: v.uuid("id_invalid_uuid"),
  },
  headerRules: {
    "x-retries": v
      .number("validators.invalid_retries")
      .int("validators.invalid_retries")
      .gte(0, "validators.invalid_retries"),
  },
  onValidationError(req, errors) {
    return view("auth.login", {
      errors,
      old: req.body,
    });
  },
});

Other common shapes:

// JSON
onValidationError(req, errors) {
  return Response.json({ code: "VALIDATION_ERROR", errors }, { status: 422 });
}

// async
async onValidationError(req, errors) {
  return await createValidationResponse(req, errors);
}

// redirect
onValidationError(req, errors) {
  return Response.redirect("/login");
}