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-plugin-chasevida

v0.1.2

Published

A variation of the ESLint space-in-parens rule that adds additional exceptions

Downloads

17

Readme

eslint-plugin-chasevida

Build Status

A variation/fork of the ESLint space-in-parens rule by Jonathan Rajavuori that adds additional exceptions.

This fork essentially allows for the below style to be valid where a negative assertion is given spacing to make it stand out when reading through the source.

if ( ! condition) {
    // do something
}

We have renamed the rule here to spaces-in-parens to avoid any conflicts. Ideally you would not include the original rule. The original ESLint rule documentation is available here.

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install eslint-plugin-spaces-in-parens:

$ npm install eslint-plugin-chasevida --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-chasevida globally.

Usage

Add spaces-in-parens to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
    "plugins": [
        "chasevida"
    ]
}

Then configure the rules you want to use under the rules section.

{
    "rules": {
        "chasevida/spaces-in-parens":   [2, "never", { "exceptions": ["!"] }]
    }
}

Supported Rules

This rule extends the core functionality of space-in-parens and should be referred to for core functionality and implementation.

The additional exceptions this plugins supports are outlined below:

Given "spaces-in-parens": [2, "never", { "exceptions": ["!"] }], the following patterns are considered problems:

/*eslint spaces-in-parens: [2, "never", { "exceptions": ["!"] }]*/

if (!condition);    /*error There must be a leading space inside this paren.*/
if ( ! condition ); /*error There must be only a leading space inside this paren.*/

The following patterns are not considered problems:

/*eslint spaces-in-parens: [2, "never", { "exceptions": ["!"] }]*/

if ( ! condition);
if ( !condition);