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 🙏

© 2025 – Pkg Stats / Ryan Hefner

verifica-core

v0.1.5

Published

[Check out the documentation!](https://radoslaw-medryk.gitbook.io/verifica/getting-started/installation)

Readme

verifica

Check out the documentation!

What is that?

Verifica is a validation library for JavaScript. It uses modern language features to make your experience as a developer as seamless as possible, and keep your code clean and nice.

Why do I need it?

There is fair choice of validation libraries out there already, so why do you need a new one? Verifica focuses on making the developer experience as good as possible, keeping the code clean. It promotes another approach to validation - rules as functions - composable, but not constraining.

How is it better?

There are a few decisions that makes Verifica developer friendly, allowing to write clean code. The biggest difference is made however by the smart way in which verifica remembers the path of the property you are validation, and decorates the possible error message with information which property exactly failed which exact rule. To show an example:

// (...)

getErrors(request.params.userId, isString);
// [{ type: "isString", path: ["request", "params", "userId"] }]

How is it useful? You can have an API that returns specific errors describing what went wrong and which exact field failed the validation, no matter how deeply nested. And without writing any additional line of code!

Where do I start?

Check out the documentation!