Tooling and Configuration for maintainable and readable code for Web Projects.
"If you want your code to be easy to write, make it easy to read." -- Robert C. Martin
fix:cssfor linting and auto formatting of CSS code.
You can copy the relevant files into your own project like
For ESLint/StyleLint there is a more sophisticated approach: The configuration can be included like shown below:
We also bundle the whole tooling aspect in here.
You can just import "readable-core" into you
gulpfile.babel.js for having easy access to some
common tasks like
Predefined tasks to import into your custom
PostCSS-based linter for CSS. Supports alternative dialects like SugarSS, SCSS and Sass.
order: Grouping and sorting of rules and properties.
css-modules: Checks whether CSS classes which are accessed via CSS modules are defined.
filenames: Validation for file names matching some common sense requirements.
flowtype: Support for checking FlowType syntax to match rules.
flowtype-errors: Helps writing correct FlowType declarations.
import: Checks whether imports map to valid entry points.
jsx-a11y: Accessibility checks for JSX tags e.g. requiring
alttags on images.
lodash: Lodash specific checks and hints to prefer common features over custom/builtin.
no-use-extend-native: Prevent extending native objects/classes like
node: Prevents usage of deprecated features and other checks when developing NodeJS based apps.
promise: Checks for correctly working with Promises.
react: React specific checks for requiring specific structures of classes + preferring functional patterns.
security: Checks for security issues in e.g. RegExps.
you-dont-need-lodash-underscore: Showcases where ES5 would be a better solution than Lodash.
Auto linting for all
.js staged files when these are about to being committed to the repository.
Sebastian Software GmbH