Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: package.json

Issue 29441570: Issue 5257 - Add an eslint target to npm run and run it posttest. (Closed) Base URL: https://hg.adblockplus.org/adblockpluscore/
Patch Set: Created May 18, 2017, 3:53 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: package.json
===================================================================
--- a/package.json
+++ b/package.json
@@ -1,15 +1,19 @@
{
"name": "adblockpluscore",
"repository": "https://hg.adblockplus.org/adblockpluscore",
"license": "GPL-3.0",
"dependencies": {},
"devDependencies": {
"chrome-remote-interface": "^0.20.0",
+ "eslint": "^3.19.0",
+ "eslint-config-eyeo": "1.0.4",
"nodeunit": "0.9.1",
"sandboxed-module": "2.0.3",
"unzip": "^0.1.11"
},
"scripts": {
- "test": "node test_runner.js"
+ "eslint": "eslint *.js lib test chrome",
Wladimir Palant 2017/05/19 15:52:31 IMHO, this will run the global ESLint and not the
hub 2017/05/19 16:47:31 $ which eslint eslint not found If I echo $PATH f
Wladimir Palant 2017/05/19 18:12:31 Good to know, definitely saves some complexity her
+ "test": "node test_runner.js",
+ "posttest": "npm run eslint"
}
}
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld