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 🙏

© 2024 – Pkg Stats / Ryan Hefner

yooda

v0.4.1

Published

🧘‍♂️600b validation library with custom handlers and messages

Downloads

12

Readme

Contents

Installation

npm add yooda

Basic Usage

import validator from "yooda";

const requestBodySchema = {
	name: {
		type: "string",
		required: true
	},
	age: {
		type: "number",
		required: true
	}
};

const requestBody = {
	name: "Ademola Adegbuyi",
	age: 23
};

try {
	const validate = validator(requestBodySchema);
	validate(requestBody);
} catch (err) {
	res.status(500).send(err);
}

That's it, really. If the value doesn't meet the requirement, it throws an error and you can handle it as you want.

Extras

Domain

This is more like a plugin, to ensure some other personal requirements are met asides from the regular "required" and "type". We definitely cannot offer a way to solve all kinds of edge-cases so we're giving you a buffet; Be your own boss, control the nature of the validation.

Here's how to use it:

const shouldStartWithA = value => value.startsWith("a");
// attach it to your schema
const requestBodySchema = {
	name: {
		type: "string",
		required: true,
		domain: [shouldStartWithA]
	}
};
const validate = validator(requestBodySchema);
validate(requestBody);

The convention you decide to pick is up to you. The one used in the example above is a function that is used on the fly. You could just create an object of domains as done in the test file. You could also have them in a separate file and import only the ones needed.

Custom Error Messages

You could define how errors will be thrown based on the supported error types (requiredError, typeError, and domainError), and it's very easy to use! A short example:

const schema: Schema = {
	age: {
		type: "number",
		required: true,
		domain: [domains.IS_POSITIVE]
	}
};

const customErrorHandlers: CustomErrorHandlers = {
	domainError: ({ value, domain }) =>
		`${value} doesn't satify the ${domain} requirement`
};

const validate = validator(schema, customErrorHandlers);

Props available to the error types:

Note that: only the props required will be suggested to you via intellisense 🙏

type RequiredErrorProps = {
	key: string;
};

type TypeErrorProps = {
	key: string;
	type: string;
	value: any;
};

type DomainErrorProps = {
	key: string;
	type: string;
	value: any;
	domain: string;
};

LICENSE

MIT