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

eslint-config-vizia

v1.5.0

Published

The common vizia linter configs.

Downloads

501

Readme

eslint-config-vizia

Common ESLint shareable config files for vizia.

Install into your project:

npm install --save eslint eslint-config-vizia

Example uses:

ES5 browser project.

Make a .eslintrc.json config file with the following in:

{
    "env": {
        "browser": true
    }
    "extends": "vizia"
}

You must specify your environment in the "env" part. You can also customize rules as you like.

ES2015 Node.js project.

As before the environment needs to be specified. Since Node 6+ has good ES2015 feature coverage, it makes sense to use ES2015 features. A sharable config is provided for ES2015 code:

{
    "env": {
        "node": true
    }
    "extends": "vizia/ES2015"
}

Internally this config extends the base vizia config.

Tests

Tests often look like bad code. They're prone to many more lines of code per file than healthy production code etc. It's recommended to have a .eslintrc.json file in your test directory to address this. ESLint extends a config found in a directory above automatically, so you only need to turn off rules that become noisy in tests. Such a file might look like:

{
    "env": {
        "mocha": true
    },
    "rules": {
        "max-statements": 'off',
        "max-lines": 'off'
    }
}