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

yajjsl

v1.0.3-r1

Published

yet another javascript json schema library

Readme

Yet Another Javascript Json Schema Library (...hehe)

rickandmorty

Yet another piece of code that tries to validate json based on types, this is NOT BASED ON THE JSON SCHEMA STANDARD which I find too verbose for my likes but that's just me. YET REJOICE BECAUSE THE OUTPUT IS MONADIC !!!!

Goals of this Library

  1. To provide type validation for entities inside a json object
  2. To provide checkif-empty/undefined validation for entities inside a json object
  3. The output of this will be the first error encountered (Wrapped in a Left) or the whole object (wrapped in a Right) aka monadic (Either Monad)

Install

npm install yajjsl

Development Goals

  1. Use Applictive-functors/Monads and it's related operations to make for readable code
  2. Use Ramda.js for other other operations
  3. Test library thoroughly

Example


const schema1 = {
        "weapon": "String",
        "pokemon": Tuple("Array", "String"),
        "pokeball": {
            "material": "String",
            "cost": "Number"
        },
	"characters": Tuple("Array", {"name": "String"})

    };

const incorrect1 = {
        "pokemon": [1, 2],
        "pokeball": {
            "material": ["Egg Nut", "Brown Nut"],
            "cost": 100
        },
	"characters": [{ "name": "Red Foreman"}, 
		       { "name": "I am Fez" }]

    };

validate(incorrect1, schema1);

// output -> Left(Tuple("weapon", undefined)) 
// tuples are based on fantasy-land-tuples

Left Output

 // note I use Tuple and Tuple2 interchangebly

 Left(Tuple("key", undefined))   // -> "key" field is undefined 
 Left(Tuple("key", false))       // -> "key" has failed schema-based-validation
 Left(Tuple("key", "empty"))     // -> "key" has an empty element ({} or [])
 Left(Tuple("Schema","invalid")) // -> schema given is invalid
 

What this is not

  1. An uber fast library

P.S

  1. This also features schema checking for validity based on some preset rules
  2. The output is based off fantasy-land compliant stuff so you should be able to use the monadic output in any monadic/ applicative-functorish chains as long as the monads/applicative-functors belong to any fantasy-land compliant library

License

MIT License

Build Status