aboutsummaryrefslogtreecommitdiffstats
path: root/package.json
diff options
context:
space:
mode:
authorTimo Tijhof <krinklemail@gmail.com>2021-05-21 21:26:26 +0100
committerTimo Tijhof <krinklemail@gmail.com>2021-05-21 21:26:26 +0100
commitaa9385ba1267e258d634be92c639e9aa91caa6bd (patch)
tree1b9f29f382bf6709413df95f3c20f47fb78b11c2 /package.json
parent401c0be5a80a474abceb48458215ab689979539c (diff)
downloadmediawikicore-aa9385ba1267e258d634be92c639e9aa91caa6bd.tar.gz
mediawikicore-aa9385ba1267e258d634be92c639e9aa91caa6bd.zip
build: Remove 'npm run api-testing-lint' command
These files are already linted by 'npm test'. For running only the tests, there is no need to lint them first. If there are critical syntax errors than Node will report these in a useful way either way. For quick feedback on the right style during development, one can use an IDE plugin that provides it even quicker. Alternatively, one could use 'eslint path/to/subset' to run only the lint step. I've added a 'npm run lint' command to make this easier, e.g. when iterating on the style for contributors without an IDE plugin that want to confirm all lint failures from CI were addressed. Change-Id: Ic09de49543e50cb5ade241b45741fbdb397f9954
Diffstat (limited to 'package.json')
-rw-r--r--package.json4
1 files changed, 2 insertions, 2 deletions
diff --git a/package.json b/package.json
index 7bef956e7000..008ef50b1f52 100644
--- a/package.json
+++ b/package.json
@@ -1,9 +1,9 @@
{
"private": true,
"scripts": {
- "api-testing": "npm run api-testing-lint && mocha --timeout 0 --recursive tests/api-testing",
- "api-testing-lint": "eslint --cache --max-warnings 0 tests/api-testing/**",
+ "api-testing": "mocha --timeout 0 --recursive tests/api-testing",
"minify-svg": "svgo --config=.svgo.config.js -q -r -f resources/src",
+ "lint": "grunt lint",
"test": "grunt lint && npm run doc",
"qunit": "grunt qunit",
"doc": "jsduck",