b043cec2d7
The running of 'grunt qunit' is unconvenient due to it only working if the user has grunt-cli installed globally, which should not be needed because it is already installed in the local directory. It could be worked around by instructing users to use `./node_modules/.bin/grunt qunit`, but it would be much simpler to instruct them to use `npm run qunit` instead. Unlike 'composer', 'npm' does not come by default with a command like 'composer exec' that one could pass a command directly without needing to register it. This is fixed in more recent versions through 'npx -c', but that's a bit too new to require in the manual, so adding it as a run-script instead. Change-Id: I2812b13dbed50612b1626a617ba65f92e212f01a
38 lines
1.1 KiB
JSON
38 lines
1.1 KiB
JSON
{
|
|
"private": true,
|
|
"scripts": {
|
|
"test": "grunt test",
|
|
"qunit": "grunt qunit",
|
|
"doc": "jsduck",
|
|
"postdoc": "grunt copy:jsduck",
|
|
"selenium": "killall -0 chromedriver 2>/dev/null || chromedriver --url-base=/wd/hub --port=4444 & grunt webdriver:test; killall chromedriver"
|
|
},
|
|
"devDependencies": {
|
|
"deepmerge": "1.3.2",
|
|
"eslint": "4.9.0",
|
|
"eslint-config-wikimedia": "0.5.0",
|
|
"grunt": "1.0.1",
|
|
"grunt-banana-checker": "0.6.0",
|
|
"grunt-contrib-copy": "1.0.0",
|
|
"grunt-contrib-watch": "1.0.0",
|
|
"grunt-eslint": "20.1.0",
|
|
"grunt-jsonlint": "1.1.0",
|
|
"grunt-karma": "2.0.0",
|
|
"grunt-stylelint": "0.9.0",
|
|
"grunt-webdriver": "2.0.3",
|
|
"karma": "1.7.1",
|
|
"karma-chrome-launcher": "2.2.0",
|
|
"karma-firefox-launcher": "1.0.1",
|
|
"karma-mocha-reporter": "2.2.5",
|
|
"karma-qunit": "1.2.1",
|
|
"nodemw": "0.11.0",
|
|
"qunitjs": "2.4.1",
|
|
"stylelint": "8.2.0",
|
|
"stylelint-config-wikimedia": "0.4.2",
|
|
"wdio-junit-reporter": "0.2.0",
|
|
"wdio-mocha-framework": "0.5.8",
|
|
"wdio-sauce-service": "^0.3.1",
|
|
"wdio-spec-reporter": "0.0.5",
|
|
"webdriverio": "4.6.2"
|
|
}
|
|
}
|