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

flipr-validation

v2.1.0

Published

Validation for flipr config data. Use this to catch bad configs before they go live.

Downloads

18

Readme

node-flipr-validation

NPM

Build Status

This project is part of the flipr family.

node-flipr-validation provides validation for flipr config data and rules. You should use it to catch bad config changes before they are deployed. Bad config deployments make flipr very unhappy.

node-flipr-validation

#Usage

const fliprValidation = require('flipr-validation');
const errors = fliprValidation({
  config: myConfigObject,
  rules: myRulesArray
});

The errors array returned by fliprValidation will be empty if there are no validation errors. If there are validation errors, the errors array will contain one or more Error objects.

Flipr Validation Options

  • config - required - object: This is the config object you want to validate.
  • rules - optional - array: The array of rules you will use against this config. If you have rules but don't provide them, some of the validation will be skipped. It's a good idea to pass the rules if you have them.

Would you like to know more?