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-node-moar

v1.0.5

Published

The linter config for people who do not want to be standard.

Downloads

30

Readme

A strict and complete ESLint configuration

License Version Build Status Known Vulnerabilities

An ESLint Shareable Config that includes this plugins and enforces reccomended:

  extends: [
    'eslint:recommended',
    'plugin:node/recommended',
    'plugin:promise/recommended',
    'plugin:security/recommended',
    'plugin:sonarjs/recommended',
  ],

And then defines:

  • a quite strict and opinionated rule set
  • formatting rules - no need for prettier
  • errors as errors, and warnings as warnings.
    • As in: if it does break it, it's an error. If it's a convention, it's a warning.

Why -moar? Because -strict was already taken and -more is boring.

Basic usage

Install all the dependencies:

yarn add -D eslint eslint-config-node-moar eslint-plugin-node eslint-plugin-security eslint-plugin-sonarjs

Create your own .eslintrc.js:

module.exports = {
  extends: [
    'node-moar',
  ],
}

Or use this one-liner:

echo "extends: ['node-moar']" > .eslintrc.yml

Get... moar :)

Part of the family are:

  • test - with linters for Jest
  • stricter - stricter lint rules enforced using more plugins