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

@slick-for/validation

v1.0.10

Published

[![Build Status](https://travis-ci.com/shavyg2/slick-for-validation.svg?branch=master)](https://travis-ci.com/shavyg2/slick-for-validation) [![Coverage Status](https://coveralls.io/repos/github/shavyg2/slick-for-validation/badge.svg?branch=master)](https

Downloads

16

Readme

@slick-for/validation

Build Status Coverage Status license

This library allows for enhanced validation with typescript support.

This gives validation as well as typescript defitions of the object it performs validation for.

Seeing is believing

(note repl.it is reporting incorrect types at time of publish vs-code reports correctly)

Online IDE Example

sync

eg


const validation = {
    name(name:string,error:string[],{path}){
        if(!is.string(name)){
            error.push(`property ${path} is required`)
        }
    }
}


const [err,person] = ValidationSync({
    name:"Sarah"
},validation)

expect(err).toBeFalsy();
expect(person.name).toBe("Sarah");

When person is returned it will have full typescript support. Autocompletion and everything just from the validation function.

async

Some times during validation you really need to validate some async process, it makes no real to have to use a different function / process to validate async paramters

eg


const validation = {
    async name(name:string,error:string[],{path}){
        if(!is.string(name)){
            error.push(`property ${path} is required`)
        }
    }
}


const [err,person] = await Validation({
    name:"Sarah"
},validation)

expect(err).toBeFalsy();
expect(person.name).toBe("Sarah");

this will work just like the sync properties and it will have all of the autocompletion on person just like the sync method.

Types

If you want to get your types while developing to use as parameters at compile time use.


const validation = {
    async name(name:string,error:string[],{path}){
        if(!is.string(name)){
            error.push(`property ${path} is required`)
        }
    }
}


type IPerson = Show<typeof validation>

//same as 

interface IPerson{
    name:string
}

This works just as well with nested and async properties.

Goal

We cannot hope to achieve a type sound system in typescript / javascript. However this will bring you 90% of the way there.

The intent is a simple as this. If you validate it, you are gauranteed to have the correct types at runtime times and you will never have your interfaces and validation functions out of sync.

This normally happens when a typescript interface is not aligned with your validation. Here since the validation is what provides the types, you ensure your interfaces are always 100% accurate.

More Examples in Repo