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

25 lines
587 B
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",
"doc": "jsduck",
"postdoc": "grunt copy:jsduck"
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": {
build: Bump various devDependencies grunt 0.4.2 -> 0.4.5 grunt-contrib-jshint 0.10.0 -> 0.11.0 grunt-jscs 0.8.1 -> 1.5.0 grunt-karma 0.9.0 -> 0.10.1 karma-firefox-launcher 0.1.3 -> 0.1.4 qunitjs 1.15.0 -> 1.17.1 Some minor fixes to pass new jscs rules; big ones postponed for now. Change-Id: I5f2348c3cf96cf5aa20eeb9083300155b3920c5b
2015-02-10 00:47:48 +00:00
"grunt": "0.4.5",
build: Declare grunt-cli dependency A long time ago, npm did not support using command line programs within 'npm test' (not unless harcoding a path to node_modules/bin/... within packages.json/scripts/test). But this has been long supported. Declaring a (dev)dependency will provide its binaries to the PATH used by the subshell 'npm test' creates internally. Add grunt-cli so that developers don't have to manually install it. Change-Id: I6a7fafa3c6e40d2407f07c514167ab9fc7661685
2015-03-19 01:08:57 +00:00
"grunt-cli": "0.1.13",
build: Upgrade grunt-banana-checker from v0.3.0 to v0.4.0 Take opportunity to drop no-longer-needed options. Change-Id: I11250c12d2123d4729e12cd0dce07b24fc5008e5
2015-10-12 18:13:48 +00:00
"grunt-banana-checker": "0.4.0",
build: Bump various devDependencies to latest * grunt-contrib-copy: 0.8.0 -> 0.8.1 * grunt-karma: 0.11.0 -> 0.12.1 * karma: 0.12.36 -> 0.13.10 * karma-chrome-launcher: 0.1.12 -> 0.2.0 * karma-qunit: 0.1.4 -> 0.1.5 All already used in other repos. Change-Id: If1548e9708aa9c8c97c9d2de14ffb4e8ada933fd
2015-09-24 15:28:53 +00:00
"grunt-contrib-copy": "0.8.1",
build: Update grunt-contrib-jshint to v0.11.3 Change-Id: I2170f77042d4f31914c684bf6bdc08321abe14db
2015-09-03 20:40:44 +00:00
"grunt-contrib-jshint": "0.11.3",
Update tests/frontend devDependencies * grunt-contrib-jshint: v0.8.0 to v0.9.2 - https://github.com/gruntjs/grunt-contrib-jshint/blob/v0.9.2/CHANGELOG - Minor changes and bug fixes - Lastest version is v0.10.0, but that embeds jshint v2.5.0 which we don't want to use yet. * grunt-contrib-watch: v0.5.3 to v0.6.1 (latest) - https://github.com/gruntjs/grunt-contrib-watch/blob/v0.6.1/CHANGELOG - Minor changes and bug fixes * grunt-jscs-checker: v0.4.0 to v0.4.1 (latest) - https://github.com/gustavohenke/grunt-jscs-checker/compare/0.4.0...0.4.1 - Minor changes Change-Id: I68e9057f8e353e2c3ac8b889977de07597211c54
2014-04-10 19:04:56 +00:00
"grunt-contrib-watch": "0.6.1",
build: Update jscs to latest * grunt-jscs: 2.5.0 → 2.6.0 Change-Id: I4b1585c557b94927e593975e2e4696b88becd095
2016-01-07 22:23:52 +00:00
"grunt-jscs": "2.6.0",
Update grunt-jsonlint to 1.0.7 This update now tells you on which line in which file the error happends. Changelog is 1.0.7 Include file name and JSON source line number in error messages 1.0.6 CJSON support thanks to @fredghosn, unit tests Change-Id: I38dc4a51416cfde0bb0434921d15f1c119abc01b
2015-12-24 14:12:42 +00:00
"grunt-jsonlint": "1.0.7",
build: Bump various devDependencies to latest * grunt-contrib-copy: 0.8.0 -> 0.8.1 * grunt-karma: 0.11.0 -> 0.12.1 * karma: 0.12.36 -> 0.13.10 * karma-chrome-launcher: 0.1.12 -> 0.2.0 * karma-qunit: 0.1.4 -> 0.1.5 All already used in other repos. Change-Id: If1548e9708aa9c8c97c9d2de14ffb4e8ada933fd
2015-09-24 15:28:53 +00:00
"grunt-karma": "0.12.1",
Update karma to 0.13.19 Bug: T122941 Change-Id: Iee84646b0f914bceb254ffc18d678d916c38eb20
2016-01-06 01:02:50 +00:00
"karma": "0.13.19",
Update packages to do with karma Packages updated are: karma-chrome-launcher updated to 0.2.0 karma-firefox-launcher updated to 0.1.7 Change-Id: I542436bf8f0d782fc2af57a170faf936271b2bf9
2015-12-26 15:17:08 +00:00
"karma-chrome-launcher": "0.2.2",
"karma-firefox-launcher": "0.1.7",
build: Bump various devDependencies to latest * grunt-contrib-copy: 0.8.0 -> 0.8.1 * grunt-karma: 0.11.0 -> 0.12.1 * karma: 0.12.36 -> 0.13.10 * karma-chrome-launcher: 0.1.12 -> 0.2.0 * karma-qunit: 0.1.4 -> 0.1.5 All already used in other repos. Change-Id: If1548e9708aa9c8c97c9d2de14ffb4e8ada933fd
2015-09-24 15:28:53 +00:00
"karma-qunit": "0.1.5",
build: Bump various devDependencies grunt-contrib-jshint: 0.11.0 -> 0.11.2 grunt-jscs: 1.5.0 -> 1.8.0 karma-chrome-launcher: 0.1.7 -> 0.1.8 qunitjs: 1.17.1 -> 1.18.0 Some trivial indentation and line-spacing changes to make this pass jscs. Change-Id: Ieeb6dbcd3e6d9f6f0fb9865d356da462b9b0499b
2015-05-01 22:37:14 +00:00
"qunitjs": "1.18.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