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-pep8-blank-lines

v0.0.8

Published

Ref: https://www.python.org/dev/peps/pep-0008/#blank-lines

Downloads

30

Readme

eslint-plugin-pep8-blank-lines

CircleCI

An ESLint blank line rule supports rule for different level. Inspired by PEP8.

Now in Beta. Not widely test.

Why

The space between chapters and between paragraphs should be different make it have good readibility. I believe source code should too. But current ESLint rules can't have different blank line rule in different level of scope.

When I write Python and found the PEP8 coding style. I fall in love with this simple but elegant rule. Basically, it allows two blank line between top level classes or functions. So I can keep more spaces between top level objects. And I decide to implement it in ESLint.

Usage

Install

NPM install and save to dev dependency.

npm install --save-dev eslint-plugin-pep8-blank-lines

Configure

Sample eslintrc:

{
  "plugins": [
    "pep8-blank-lines",
  ],

  "rules": {
    "pep8-blank-lines/pep8-blank-lines": 2
  }
}

If your config based on other config style. You might need to disable some rule related to blank lines. Take standard for example:

{
  "extends": "standard",

  "plugins": [
    "pep8-blank-lines",
    "no-parameter-e"
  ],

  "rules": {
    "semi": [2, "always"],
    "no-extra-semi": 2,
    "comma-dangle": ["error", "always-multiline"],
    "no-multiple-empty-lines": 0,
    "pep8-blank-lines/pep8-blank-lines": 2,
    "no-parameter-e/no-parameter-e": 2
  }
}