Thijs/wiki.techinc.nl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
wiki.techinc.nl/package.json

41 lines
1.2 KiB
JSON
Raw Normal View History

Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
{
build: Set private flag in package.json (for now) This fixes the warning about missing package description and license. This matches what we do elsewhere for dev-only npm pipelines. Change-Id: I29ee43482b90ea8875a5376409d656648e3c4b27
2015-09-26 13:32:06 +00:00
"private": true,
Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
"scripts": {
Rename JSDuck config to standard 'jsduck' * Move configuration to /jsduck.json per standard. This way it can be run as plain '$ jsduck' without needing a maintenance script or custom Jenkins job. Similar to JSHint, JSCS, Grunt, and Gem etc. * Move --processes=0 from maintenace script into config file. This should've been in the config file all along and serves as workaround for https://github.com/senchalabs/jsduck/issues/525. * Use grunt-contrib-copy instead of a symlink for resources. For local development a symlink works fine, but for publishing from Jenkins to doc.wikimedia.org the /docs/js/ directory needs to be standalone. This was previously done with a manual post-build step that added an additional rsync, but this logic should be in the repository so that the doc entry point can be simplified and standardised to 'npm run-script doc' for all projects. Change-Id: Iaaaac50ee78dd9ff8f24f1ef3a3685ad51cf33b2
2015-03-08 17:34:06 +00:00
"test": "grunt test",
build: Add 'npm run qunit' command 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
2017-11-22 18:48:27 +00:00
"qunit": "grunt qunit",
Rename JSDuck config to standard 'jsduck' * Move configuration to /jsduck.json per standard. This way it can be run as plain '$ jsduck' without needing a maintenance script or custom Jenkins job. Similar to JSHint, JSCS, Grunt, and Gem etc. * Move --processes=0 from maintenace script into config file. This should've been in the config file all along and serves as workaround for https://github.com/senchalabs/jsduck/issues/525. * Use grunt-contrib-copy instead of a symlink for resources. For local development a symlink works fine, but for publishing from Jenkins to doc.wikimedia.org the /docs/js/ directory needs to be standalone. This was previously done with a manual post-build step that added an additional rsync, but this logic should be in the repository so that the doc entry point can be simplified and standardised to 'npm run-script doc' for all projects. Change-Id: Iaaaac50ee78dd9ff8f24f1ef3a3685ad51cf33b2
2015-03-08 17:34:06 +00:00
"doc": "jsduck",
Selenium tests in Node.js using WebdriverIO Introduce the WebdriverIO browser testing framework driven by Node.js. The overall intents are: * have MediaWiki core to provide a platform to run tests that is shared between core and the extensions. * phase out ruby driven browser tests eventually. Code is namespaced in sub directory /tests/selenium The 'pages' sub directory provides helper representing a MediaWiki page such as Special:Login and human friendly helpers to interact with the elements. Add Grunt task webdriver:test. Provide a npm script to easily spawn/dispose chromedriver and run above grunt task. wdio.conf.js provides all the configuration. It defaults to point to a MediaWiki-Vagrant installation on http://127.0.0.1:8080. Can be overriden with environment settings as needed. glob patterns (specs) are made absolute paths from MediaWiki root path that let us run the tests either from the root path (eg the npm wrapper or from the tests/selenium directory when invoking wdio directly. wdio assumes they are relative to the current working directory, hence the normalization. wdio.conf.jenkins.js extends the configuration and is used solely for Jenkins. The switch is done from the Gruntfile.js whenever JENKINS_HOME is set. Specially we want junit reports to be generated. Provide a more specific eslint configuration. References: * MALU https://phabricator.wikimedia.org/source/malu/ * T151442 Research WebdriverIO * T151443 Research Nightwatch.js Bug: T139740 Signed-off-by: Antoine Musso <hashar@free.fr> Change-Id: Ibe7a004a120e82af637ab3e31b725de743134c99
2016-12-19 16:39:29 +00:00
"postdoc": "grunt copy:jsduck",
npm selenium command, use bash On Windows this seems to complain unless bash is specified Change-Id: I4515c851ffea143d4c1c6d111ffdd64b62f9f304
2018-06-07 16:15:30 +00:00
"selenium": "bash ./tests/selenium/selenium.sh",
selenium: Run wdio directly without grunt Doesn't seem to add anything, except complexity. This has the benefit of matching more closely the way the README recommends running individual tests. Also add a check for 'chromedriver' before running it. Normally the -e and pipefail would suffice, but because it runs in the background, the error can be buried, hard to find, or even not cause exit code to be set properly. Thus, do a simple 'hash' check that will print a useful command and exit cleanly. Before: > $ something & > [1] 57922 > -bash: something: command not found > [1]+ Exit 127 something > $ echo $? > 0 After: > $ hash something > -bash: hash: something: not found > (exit: 1) $ echo $? > 1 Change-Id: Id95f18927b5443defe679a77a82c5cbdd127c716
2018-04-21 01:10:56 +00:00
"selenium-test": "wdio ./tests/selenium/wdio.conf.js"
Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
},
"devDependencies": {
Selenium tests in Node.js using WebdriverIO Introduce the WebdriverIO browser testing framework driven by Node.js. The overall intents are: * have MediaWiki core to provide a platform to run tests that is shared between core and the extensions. * phase out ruby driven browser tests eventually. Code is namespaced in sub directory /tests/selenium The 'pages' sub directory provides helper representing a MediaWiki page such as Special:Login and human friendly helpers to interact with the elements. Add Grunt task webdriver:test. Provide a npm script to easily spawn/dispose chromedriver and run above grunt task. wdio.conf.js provides all the configuration. It defaults to point to a MediaWiki-Vagrant installation on http://127.0.0.1:8080. Can be overriden with environment settings as needed. glob patterns (specs) are made absolute paths from MediaWiki root path that let us run the tests either from the root path (eg the npm wrapper or from the tests/selenium directory when invoking wdio directly. wdio assumes they are relative to the current working directory, hence the normalization. wdio.conf.jenkins.js extends the configuration and is used solely for Jenkins. The switch is done from the Gruntfile.js whenever JENKINS_HOME is set. Specially we want junit reports to be generated. Provide a more specific eslint configuration. References: * MALU https://phabricator.wikimedia.org/source/malu/ * T151442 Research WebdriverIO * T151443 Research Nightwatch.js Bug: T139740 Signed-off-by: Antoine Musso <hashar@free.fr> Change-Id: Ibe7a004a120e82af637ab3e31b725de743134c99
2016-12-19 16:39:29 +00:00
"deepmerge": "1.3.2",
build: Bump eslint devDependencies to latest eslint 3.12.2 → 4.9.0 grunt-eslint 20.0.0 → 20.1.0 Change-Id: I7eb9964fb5d163c5bbcef850f62383cbceb59287
2017-10-25 19:52:10 +00:00
"eslint": "4.9.0",
build: Bump eslint-config-wikimedia from 0.4.0 to 0.5.0 Change-Id: I06010cd6367c1884b5536e7929d3345feba7f305
2017-08-22 00:06:02 +00:00
"eslint-config-wikimedia": "0.5.0",
build: Introduce eslint-plugin-qunit and enforce Change-Id: Iefe06cc865c458000ca5350c2d9205f5b768bac8
2018-06-05 20:58:25 +00:00
"eslint-plugin-qunit": "3.2.1",
Update grunt and grunt-contrib-watch to resolve vulnerabilities `npm audit` found 27 vulnerabilities (11 low, 12 moderate, 4 high). `npm audit fix` fixed most of them. There are 8 vulnerabilities remaining (2 low, 6 moderate). Bug: T194280 Change-Id: I05d80bc38d16be8249a27d94dad8e13c65139545
2018-06-15 11:46:46 +00:00
"grunt": "1.0.3",
build: Bump grunt-banana-checker from 0.5.0 to 0.6.0 Change-Id: I64d4267d20716b893237f7f13729343593c8d382
2017-03-28 19:08:05 +00:00
"grunt-banana-checker": "0.6.0",
build: Bump npm development dependencies to latest grunt-contrib-copy 0.8.2 → 1.0.0 grunt-contrib-watch 0.6.1 → 1.0.0 karma 0.13.19 → 0.13.22 Change-Id: Idc5c1ac97580e91d9c958c55cdfdda681330c254
2016-03-17 19:45:21 +00:00
"grunt-contrib-copy": "1.0.0",
Update grunt and grunt-contrib-watch to resolve vulnerabilities `npm audit` found 27 vulnerabilities (11 low, 12 moderate, 4 high). `npm audit fix` fixed most of them. There are 8 vulnerabilities remaining (2 low, 6 moderate). Bug: T194280 Change-Id: I05d80bc38d16be8249a27d94dad8e13c65139545
2018-06-15 11:46:46 +00:00
"grunt-contrib-watch": "1.1.0",
build: Bump eslint devDependencies to latest eslint 3.12.2 → 4.9.0 grunt-eslint 20.0.0 → 20.1.0 Change-Id: I7eb9964fb5d163c5bbcef850f62383cbceb59287
2017-10-25 19:52:10 +00:00
"grunt-eslint": "20.1.0",
build: Bump jsonlint devDependency to latest grunt-jsonlint 1.0.7 → 1.1.0 We can't bump the karma/qunit modules due to issues with our CI. Change-Id: I15595df8b30a8ef4ddb6471acdd8d4da4f4afabc
2016-11-16 22:45:14 +00:00
"grunt-jsonlint": "1.1.0",
build: Bump grunt-karma and related tools to 1.0.x Also bump karma to 1.1.0 see changelog at https://github.com/karma-runner/karma/releases please Change-Id: Ic982dfc7ccebeecd6082b5476372cbb87fec5f1b
2016-06-28 17:12:45 +00:00
"grunt-karma": "2.0.0",
build: Bump devDependencies to latest grunt-stylelint 0.9.0 → 0.10.0 stylelint 8.2.0 → 9.2.0 stylelint-config-wikimedia 0.4.2 → 0.4.3 Change-Id: I612cf96d99e2af67b3f7ef3284657f66f3e18d2e
2018-04-05 00:37:11 +00:00
"grunt-stylelint": "0.10.0",
build: Update Karma to v2.0.2 The current version has a couple of dependencies with high severity vulnerabilities. Bug: T194280 Change-Id: I3f9f36a6a5c2ba1716b91d14e59bc60f9e0ff513
2018-05-10 15:04:32 +00:00
"karma": "2.0.2",
build: Bump karma devDependencies to latest karma 1.5.0 → 1.7.1 karma-chrome-launcher 2.0.0 → 2.2.0 karma-mocha-reporter 2.2.3 → 2.2.5 nodemw 0.10.1 → 0.11.0 qunitjs 2.4.0 → 2.4.1 Change-Id: I1e06189a12fbbc1d62781a4636f192c5b7078c1a
2017-10-25 19:53:56 +00:00
"karma-chrome-launcher": "2.2.0",
build: Update karma to 1.5.0, karma-firefox-launcher to 1.0.1 karma: Changelog at https://github.com/karma-runner/karma/releases https://github.com/karma-runner/karma/compare/v1.1.0...v1.5.0 karma-firefox-launcher: Changelog at https://github.com/karma-runner/karma-firefox-launcher/blob/master/CHANGELOG.md#101-2017-03-04 https://github.com/karma-runner/karma-firefox-launcher/compare/v1.0.0...v1.0.1 Karma v1.1.1 added use of `<script crossorigin="anonymous">` for the urls it initially loads. While most requests will be done by MW itself directly (and served locally via the proxy at /w/) the initial request cannot come from the proxy and is loaded from wgServer directly. Therefore we need to set crossOriginAttribute=false to override the new default that v1.1.1 introduced. Change-Id: I9f5067b949c0a77e46f47c2a110a7b5df5953fda
2017-03-20 19:25:36 +00:00
"karma-firefox-launcher": "1.0.1",
build: Bump karma devDependencies to latest karma 1.5.0 → 1.7.1 karma-chrome-launcher 2.0.0 → 2.2.0 karma-mocha-reporter 2.2.3 → 2.2.5 nodemw 0.10.1 → 0.11.0 qunitjs 2.4.0 → 2.4.1 Change-Id: I1e06189a12fbbc1d62781a4636f192c5b7078c1a
2017-10-25 19:53:56 +00:00
"karma-mocha-reporter": "2.2.5",
build: Switch QUnit package from deprecated 'qunitjs' to 'qunit' This should fix the deprecation warning from npm in CI logs. Change-Id: I5d02dd8d6a86123d7935db51b8d0b5d88218869f
2018-04-23 15:32:50 +00:00
"karma-qunit": "2.0.1",
build: Bump postcss-less up to 1.1.5 from 1.1.3 Problem over, we think. Bug: T190269 Change-Id: I0a94c99fb75613b03f15954512744dec63fd779e
2018-04-05 00:43:15 +00:00
"postcss-less": "1.1.5",
build: Update Karma's qunit from 2.5.0 to 2.6.0 Follows-up 065b21b4bd which updated the copy of QUnit used on Special:JavaScriptTest. Change-Id: I24b17c9c266f58d48caa9c3392496c469b3ddba0
2018-05-10 13:12:17 +00:00
"qunit": "2.6.0",
build: Bump devDependencies to latest grunt-stylelint 0.9.0 → 0.10.0 stylelint 8.2.0 → 9.2.0 stylelint-config-wikimedia 0.4.2 → 0.4.3 Change-Id: I612cf96d99e2af67b3f7ef3284657f66f3e18d2e
2018-04-05 00:37:11 +00:00
"stylelint": "9.2.0",
"stylelint-config-wikimedia": "0.4.3",
Selenium tests in Node.js using WebdriverIO Introduce the WebdriverIO browser testing framework driven by Node.js. The overall intents are: * have MediaWiki core to provide a platform to run tests that is shared between core and the extensions. * phase out ruby driven browser tests eventually. Code is namespaced in sub directory /tests/selenium The 'pages' sub directory provides helper representing a MediaWiki page such as Special:Login and human friendly helpers to interact with the elements. Add Grunt task webdriver:test. Provide a npm script to easily spawn/dispose chromedriver and run above grunt task. wdio.conf.js provides all the configuration. It defaults to point to a MediaWiki-Vagrant installation on http://127.0.0.1:8080. Can be overriden with environment settings as needed. glob patterns (specs) are made absolute paths from MediaWiki root path that let us run the tests either from the root path (eg the npm wrapper or from the tests/selenium directory when invoking wdio directly. wdio assumes they are relative to the current working directory, hence the normalization. wdio.conf.jenkins.js extends the configuration and is used solely for Jenkins. The switch is done from the Gruntfile.js whenever JENKINS_HOME is set. Specially we want junit reports to be generated. Provide a more specific eslint configuration. References: * MALU https://phabricator.wikimedia.org/source/malu/ * T151442 Research WebdriverIO * T151443 Research Nightwatch.js Bug: T139740 Signed-off-by: Antoine Musso <hashar@free.fr> Change-Id: Ibe7a004a120e82af637ab3e31b725de743134c99
2016-12-19 16:39:29 +00:00
"wdio-junit-reporter": "0.2.0",
selenium: Initial version of wdio-mediawiki package This is new package will be reusable by other repositories for their browser tests, without having to reference the internal selenium/pageobjects/ directory from MediaWiki core. In addition to not requiring direct imports, it will also avoid problems in the future by allowing the package to be versioned and iterated upon without forcing an atomic global upgrade (or broken master builds), everytime we change something. See wdio-mediawiki/README for details. Within MediaWiki core itself, the package is used using the 'file' specifier in its package.json, so that we always test and develop using its working copy, which makes drafting and testing changes easier. Also misc changes to make wdio.conf easier to understand. Bug: T193088 Change-Id: I547a7899e7a97693a93567dd763784e637433d55
2018-05-02 17:48:24 +00:00
"wdio-mediawiki": "file:tests/selenium/wdio-mediawiki",
Fix a critical NPM package vulnerability NPM v6 audits packages during installation. This is the only critical vulnerability. Bug: T194280 Change-Id: I5fe35067919ad67b9781701136e290eda17c3afa
2018-05-10 12:13:45 +00:00
"wdio-mocha-framework": "0.5.13",
Selenium: Upgrade WebdriverIO to 4.12.0 Bug: T180144 Change-Id: I8d34e2240fe76798c99315a54ea5bab63b2409e9 Depends-On: Ic69be92c2b0b7a08a9b8cc417a40ebb38f249ea3
2018-03-13 13:30:43 +00:00
"wdio-sauce-service": "0.3.1",
Selenium tests in Node.js using WebdriverIO Introduce the WebdriverIO browser testing framework driven by Node.js. The overall intents are: * have MediaWiki core to provide a platform to run tests that is shared between core and the extensions. * phase out ruby driven browser tests eventually. Code is namespaced in sub directory /tests/selenium The 'pages' sub directory provides helper representing a MediaWiki page such as Special:Login and human friendly helpers to interact with the elements. Add Grunt task webdriver:test. Provide a npm script to easily spawn/dispose chromedriver and run above grunt task. wdio.conf.js provides all the configuration. It defaults to point to a MediaWiki-Vagrant installation on http://127.0.0.1:8080. Can be overriden with environment settings as needed. glob patterns (specs) are made absolute paths from MediaWiki root path that let us run the tests either from the root path (eg the npm wrapper or from the tests/selenium directory when invoking wdio directly. wdio assumes they are relative to the current working directory, hence the normalization. wdio.conf.jenkins.js extends the configuration and is used solely for Jenkins. The switch is done from the Gruntfile.js whenever JENKINS_HOME is set. Specially we want junit reports to be generated. Provide a more specific eslint configuration. References: * MALU https://phabricator.wikimedia.org/source/malu/ * T151442 Research WebdriverIO * T151443 Research Nightwatch.js Bug: T139740 Signed-off-by: Antoine Musso <hashar@free.fr> Change-Id: Ibe7a004a120e82af637ab3e31b725de743134c99
2016-12-19 16:39:29 +00:00
"wdio-spec-reporter": "0.0.5",
Selenium: Upgrade WebdriverIO to 4.12.0 Bug: T180144 Change-Id: I8d34e2240fe76798c99315a54ea5bab63b2409e9 Depends-On: Ic69be92c2b0b7a08a9b8cc417a40ebb38f249ea3
2018-03-13 13:30:43 +00:00
"webdriverio": "4.12.0"
Set up node-jscs via Grunt (and pass it) * Set up Grunt via package.json (run `npm install` in mediawiki-core) * Add grunt task for node-jscs (NEW) This is a style checker (as opposed to jshint, which is for code quality). There are a few small style-related things that JSHint can check (camelcase, onevar etc.) but those are being deprecated in JSHint v3, people should use more sophisticated tools like node-jscs for this instead. As such this commit removes moves of those options from our jshint configuration. See: http://jshint.com/blog/jshint-3-plans/ * Add grunt task for jshint This will use the same jshint configuration as we use on Jenkins but makes it easier to run locally from the command line by being part of the same `$ grunt test` task list. Also: * Changed jshintignore to use "dir/**"" instead of "/dir" or "dir" because the latter is not compatible with Grunt for some reason. See also https://github.com/gruntjs/grunt-contrib-jshint/issues/126. Examples of coding style rules that were being violated that we can now catch in node-jscs: * Operator "," should stick to preceding expression * Missing space after "if" keyword * Multiple line break * Empty block (in jquery.textSelection and mediawiki.language) Bug: 54218 Change-Id: Ib9d7eab9f0d5cea5fb33f0b9f82e5554897fdfe0
2014-01-31 02:03:11 +00:00
}
}
Reference in a new issue Copy permalink