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

@wemaintain/eslint-config

v4.0.5

Published

### eslint For the basic JS code style, we use the `StandardJS` preset You can find the rules [here](https://standardjs.com/rules.html#javascript-standard-style).

Downloads

20

Readme

WeMaintain code style

eslint

For the basic JS code style, we use the StandardJS preset You can find the rules here.

tslint

On top of this config, we have to use the Typescipt parser to build an understandable AST for ESLint and the the @typescript-eslint/eslint-plugin to add custome rules for typescript.

Set up your project

  1. Install the eslint config:

    yarn add -D @wemaintain/eslint-config
  2. Install all peerDependencies of this config:

    yarn add -D $(npm view --json "@wemaintain/eslint-config" peerDependencies | sed 's/\":\ \"/@/g' | sed '1d;$d' | sed 's/,//g' | sed 's/\"//g' | sed -e :a -e '$!N; s/\n//; ta')
  3. Create your tsconfig.json file with this minimal configuration:

    {
        "extends": [
            "@wemaintain/eslint-config/tsconfig.default.json" 
        ]       
    }

    Or simply:

    cp node_modules/@wemaintain/eslint-config/preconfig/tsconfig.json .

    Your tsconfig.json should extend the default tsconfig to set basics options for the compiler, like use es6 libraies, enable decorators, use strict mode, ect.

    See all other compiler options

  4. Create the .eslintrc.json (or copy the .eslintrc.json from this repository) with this minimal configuration:

    {
        "extends": [
            "@wemaintain/eslint-config"
        ],
        "parserOptions": {
            "project": "/path/of/your/tsconfig.json"
        }
    }

    Or simply:

    cp node_modules/@wemaintain/eslint-config/preconfig/.eslintrc.json .

    Your .eslintrc.json should extend the default eslint presets which, itself inherits from the standardJS rules code style for javascript and typescript-eslint recommended rules for typescript as well as some additional rules.

(For VSCode) Auto format on save from eslint rules

  1. Install the extension dbaeumer.vscode-eslint
  2. Add the following to your vs-code settings (or copy the .vscode folder into you project from this repository) :
    {
         "javascript.format.enable": false,
         "typescript.format.enable": false,
         "editor.formatOnSave": false,
         "eslint.enable": true,
         "eslint.validate": [
             "javascript",
             "typescript",
         ],
         "[typescript]": {
             "editor.defaultFormatter": "dbaeumer.vscode-eslint"
         },
         "eslint.alwaysShowStatus": true,
         "editor.codeActionsOnSave": {
             "source.fixAll.eslint": true 
         },
         "editor.detectIndentation": false,
         "editor.tabSize": 2
    }
    Or simply:
    cp -r node_modules/@wemaintain/eslint-config/preconfig/.vscode/ .

Now when you save the file, the formatter will auto fix some code style errors.