Package Exports
- exlint
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 (exlint) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Exlint
A self-contained eslint profile that requires no boilerplate setup such as installing several profiles and plugins. Uses babel-eslint out of the box for bleeding-edge ES6/ES7.
How to Use
Use exlint the same way you would use eslint, without any boilerplate setup.
# globally
npm install exlint -g
# or locally
npm install exlint --save-dev
exlint path/to/dirRules
exlint is based on standard with a few tweaks based on my personal coding preference. The following rules are enforced on top of standard.
- Use a comma dangle with multiline objects
- Use open spacing in objects
- Good:
{ my: 'object' } - Bad:
{my: 'object'}
- Good:
- Wrap arrow function parameters in parentheses
- Good:
(t) => {} - Bad:
t => {}
- Good:
- Use the correct order for requiring/importing modules: native node modules, installed modules, custom modules in the same directory, then custom modules in upper directories
- Good:
import path from 'path' import namor from 'namor' import other from './other' - Bad:
import namor from 'namor' import other from './other' import path from 'path'
- Good: