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

@lankajs/yup

v1.0.1

Published

module: The one package in the family a yup application cannot work without: a synchronous bridge.

Readme

@lankajs/yup

▸ module · yup conveniences

The one package in the family a yup application cannot work without: a synchronous bridge.

A library in the same box. The app imports and calls it; core does not know it exists.

Runs in: the browser, node and React Native — everywhere.

How to use it: GUIDE.md — the user guide, with examples. How to change it: SKILL.md.

Contents

  • lankaYupValidator — the synchronous bridge, because yup's Standard Schema is async
  • TLankaInferred<S> — schema type inference

Why this package is not optional

Every other package in modules/validators/ exists to make a CHOICE visible: core already accepts the library's schemas and the package is a name. This one is different.

yup does implement Standard Schema — since 1.7.x — but its ~standard.validate is declared async and therefore returns a promise for every schema, valid or not. The framework's validation port is SYNCHRONOUS and refuses a promise loudly, on purpose: a port that answered "fine" to a value it never inspected would let unvalidated data through. So without this package a yup schema cannot be validated by lanka at all — not slowly, not partially: every call throws.

The bridge is validateSync(value, { abortEarly: false }), which yup has had all along. It lives here rather than in core for the same reason the zod 3 bridge does: it is knowledge about a specific library and a specific version, and core knows only the protocol.

What the bridge has to translate

Three things, each found by a test rather than by reading the documentation:

  • Paths are bracketed. yup says tags[0].id; ILankaFieldError.path is segments, so it becomes ["tags", 0, "id"] and the message string stays tags.0.id: …, which is how the whole family reads.
  • A top-level failure has no path. yup.number().min(18) refusing 3 reports path: undefined, which is the form's ROOT rather than an input named "".
  • An async test cannot run synchronously. yup throws a plain Error saying so. Passed through as-is it would reach a consumer as a stray library error; it comes back as the port's own loud refusal instead.

Repository map: ../../../README.md