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

scniro-validator

v1.0.1

Published

a simple email validator with corrective action capabilities

Downloads

3

Readme

a small, dependency-free email validator with configurable rules and suggested corrections

Install

npm install scniro-validator --save

Sample usage

var v = require('scniro-validator');

var result = v.validate('[email protected]');
// {valid: true}

Configuration

validation may be influenced by calling optional .init with a configuration object

var rules = {
    tld: {
        allowed: ['com']
    sdl: {
        allowed: ['bar']
    }
}

var result = v.validate('[email protected]');
// {valid: false}

Corrections

validation will include a suggested correction base on corrections defined via tld and sld supplied match objects (top-level domain and second-level domain, respectively). Specify this via tryCorrect.

var rules = {
    tld: {
        allowed: ['com'],
        corrections: [
            {match: 'con.au', correct: 'com'}
        ]
    }
}

var result = v.validate('[email protected]', {tryCorrect: true});
// {valid: false, correction: '[email protected]'}

or a really barged example

var rules = {
    tld: {
        allowed: ['com'],
        corrections: [
            {match: 'con.au', correct: 'com'}
        ]
    },
    sdl: {
        allowed: ['bar']
    }
}

var result = v.validate('foo.bar.con.au', {tryCorrect: true});
// {valid: false, correction: '[email protected]'}

Note

e-mail validation is a rabbit whole, and this tool does not aim to be a silver bullet. The capability of this tool is influenced from the w3c type="email" validation, ships with some extensibility specific to a business defined problem, and is pessimistic in nature. For a less problem-specific validation tool, check out the awesome mailcheck.js