@novemberborn/as-i-preach v11.0.0

as-i-preach

Like standard, with additional configuration:

• Uses babel-eslint so experimental syntax can be linted
• Various ESLint rules to restrict allowed syntax
• Rules for AVA tests
• Rules that enforce how dependencies are imported
• Rules to avoid potential security issues
• Rules for promises
• Rules for JSX / React
• Various awesome ESLint rules
• TypeScript support!

See .eslintrc.js and .typescript.eslintrc.js for details.

It's what I use.

Installation

$ npm install --save-dev @novemberborn/as-i-preach

Then add it to your package.json:

{
  "scripts": {
    "lint": "as-i-preach"
  }
}

Configuration

You can provide configuration in your package.json under the as-i-preach key:

{
  "as-i-preach": {
    "ignore": [
      "tmp.js"
    ]
  }
}

See standard-engine for details.

Additionally you can provide the following options:

• allowDevDependencies: a string or array of glob patterns for files that are allowed to use devDependencies.

  Defaults to ["scripts/**/*.js", "test.js", "test/**/*.js"]

• fakeDependencies: a string or array of regular expression patterns for dependency sources that are actually fake, and must not be linted.

  For example if you use babel-plugin-files, specify "^files:" to avoid linter errors for import statements that are handled by the plugin.

• resolvers: a valid value for the eslint-plugin-import's import/resolver setting

Semantic versioning

ESLint config and plugin dependencies are pinned. Any rule or plugin addition that restricts the rules is considered a breaking change.