Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .travis.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
language: node_js
node_js:
- node # Current
- 10 # Latest LTS
- 8
- 6 # Minimum supported
before_script:
npm run lint
cache:
directories:
- $HOME/.npm
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

[![NPM](https://nodei.co/npm/eslint-plugin-more.png?compact=true)](https://npmjs.org/package/eslint-plugin-more)

[![Build Status](https://travis-ci.org/WebbyLab/eslint-plugin-more.svg?branch=master)](https://travis-ci.org/WebbyLab/eslint-plugin-more)

Eslint is a very great tool and it already has tons of rules. Eslint allows us to reduce amount of time required for code review. But, of course, eslint cannot cover all the issues. So, we do in the following way, if during code review we see, that we comment on thing that is possible to check automatically, then we create new eslint rule.

Some of this rules will go to upstream after proving them in our codebase.
Expand Down
7 changes: 4 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,12 @@
"type": "git",
"url": "git@github.com:WebbyLab/eslint-plugin-more.git"
},
"engines" : {
"node" : ">=6.0.0"
"engines": {
"node": ">=6.0.0"
},
"scripts": {
"lint": "eslint ./"
"lint": "eslint ./",
"test": "find tests -type f -exec echo -n ▸ {} \\; -exec node {} \\; -exec echo ' ✓' \\;"
},
"devDependencies": {
"babel-eslint": "^7.1.1",
Expand Down