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

@asd14/eslint-config

v10.3.0

Published

JavaScript ESLint rules

Downloads

175

Readme

CircleCI npm version

JavaScript ESLint rules

JavaScript ESLint bundle with best practices and common use rules for writing more consistent code.

"semi": [ "error", "never" ] :godmode: ... the horror :goberserk:

Other similar bundles: XO, eslint-config-airbnb, eslint-config-google, more


Install

npm install @asd14/eslint-config --save-dev

Targets

Run npm info "@asd14/eslint-config@latest" peerDependencies to get the base packages needed.

It should be something like:

"eslint": "^8.13.0",
"prettier": "^2.6.0"

Add these packages to your devDependencies in package.json.

Node.js

Link ESLint to node target.

// .eslintrc
{
  "extends": [
    "@asd14/eslint-config/targets/node",
  ]
}

Node.js with Typescript

Link ESLint to node-ts target.

// .eslintrc
{
  "extends": [
    "@asd14/eslint-config/targets/node-ts",
  ]
}

React

Link ESLint to react target.

// .eslintrc
{
  "extends": [
    "@asd14/eslint-config/targets/react",
  ]
}

Inside

  • eslint-plugin-jsdoc - JSDoc specific linting rules
  • eslint-plugin-import - Support for ES2015+ (ES6+) import/export syntax
  • eslint-plugin-promise - Enforce best practices for JavaScript promises
  • eslint-plugin-unicorn - Various awesome ESLint rules
  • eslint-plugin-html - Allows linting and fixing inline scripts contained in HTML files
  • eslint-plugin-react - React specific linting rules
  • eslint-plugin-react-hooks - Linting rules rules of React Hooks.
  • eslint-plugin-no-inferred-method-name - In ES6, compact methods and unnamed function expression assignments within object literals do not create a lexical identification (name) binding that corresponds to the function name identifier for recursion or event binding. The compact method syntax will not be an appropriate option for these types of solutions, and a named function expression should be used instead. This custom ESLint rule will identify instances where a function name is being called and a lexical identifier is unavailable within a compact object literal.
  • @typescript-eslint/parser - ESLint parser which leverages TypeScript ESTree to allow for ESLint to lint TypeScript source code.
  • @typescript-eslint/eslint-plugin - ESLint plugin which provides lint rules for TypeScript codebases.

Example config

Using babel-eslint and eslint-import-resolver-webpack

.eslintrc

{
    "root"  : true,
    "parser": "babel-eslint",

    "extends": [ "@asd14/eslint-config/targets/react" ],

    "settings": {
        // Use webpack to resolve modules in imports
        "import/resolver": {
            "webpack": {
                "config": "./webpack.config.js",
            },
        },

        // Recommended if you use eslint_d
        "import/cache": {
            "lifetime": 5,
        },

        // List of regex strings that, if matched by a path, will not report
        // the matching module if no exports are found.
        "import/ignore": [ "\\.(sass|scss|less|css)$" ],
    },

    // Custom rules
    "rules": {
    },
}

.prettierrc

{
  "semi": false,
  "printWidth": 80,
  "tabWidth": 2,
  "useTabs": false,
  "singleQuote": false,
  "trailingComma": "es5",
  "bracketSpacing": true,
  "bracketSameLine": true,
  "arrowParens": "avoid"
}

Optional .editorconfig

root = true

[*]
charset = utf-8
indent_style = space
indent_size = 2
end_of_line = lf
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

Changelog

See the releases section for details.