Package Exports

eslint-config-tidy-react
eslint-config-tidy-react/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-config-tidy-react) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-config-tidy-react

ESLint shareable config for React with Tidy style

Note that this only enables rules related to React. You probably want to compose this with other configs, such as eslint-config-tidy (as shown below), to make your perfect setup.

Why?

Consistency.
Clarity.
Simplicity.

Install

npm install eslint-config-tidy eslint-config-tidy-react eslint-plugin-react --save-dev

Usage

All you have to do is tell your linter to use this config.

Use with XO (recommended)

Add some XO config to your package.json:

{
    "name": "my-awesome-project",
    "xo": {
        "extend": ["tidy", "tidy-react"]
    }
}

Alternatively, use with ESLint

Add some ESLint config to your package.json:

{
    "name": "my-awesome-project",
    "eslintConfig": {
        "extends": ["tidy", "tidy-react"]
    }
}

eslint-config-tidy - ESLint shareable config for Tidy style
XO - Linter based on ESLint

Contributing

See our contributing guidelines for more details.

Fork it.
Make a feature branch: git checkout -b my-new-feature
Commit your changes: git commit -am 'Add some feature'
Push to the branch: git push origin my-new-feature
Submit a pull request.

License

Go make something, dang it.