wikimedia/mediawiki-extensions-VisualEditor
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor synced 2024-11-28 16:20:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Visual.../package.json

24 lines
592 B
JSON
Raw Normal View History

Implement Grunt support (grunt jshint,csslint,qunit,watch) This has no influence on Jenkins but can be used locally to easily run certain tools. Since we already had `.jshintrc` in our repo it was already possible to easily run JSHint from the command-line locally. Taking that as a base the following are new features: * `grunt csslint`: Runs CSSLint on all css files * `grunt qunit`: Runs QUnit (standalone) tests in PhantomJS * `grunt test`: Runs jshint/csslint/qunit * `grunt watch`: Runs the "test" command automatically whenever a file is changed. You can keep this in the background so whenever you save a file in your editor (e.g. Sublime Text) it'll run the tests and if there is a failure, it'll throw a bash error code causing your Terminal application to beep you in whatever way your operating system does so (e.g. for Mac OS X a red badge + jumping icon in the Dock). It will continue to run in the background even after a failure so no need to re-start watch after a failure. * `grunt`: Runs the default task, which is 'test'. Previously to use `jshint .` you had to: * One-time install: * install package -- nodejs npm * npm install -g jshint * Usage: * cd VisualEditor; jshint . Now, for grunt: * One-time install: * install package -- nodejs npm * npm install -g grunt-cli * cd VisualEditor; npm install * Usage: * cd VisualEditor; grunt Change-Id: I7a4fdf4b6bf3f00cef15dc3e2c81eceb595aec7c
2013-05-31 02:33:12 +00:00
{
"name": "visualeditor",
"version": "0.0.0",
build: Remove 'repository' and 'licenses' key from package.json This isn't a node.js package, but simply the packages for the workflow in developing the extension. This repo already has other entry points and outings for this information. Change-Id: Ide13e863546e6efda61086e3daf9cdfe4ed5f1ac
2014-10-11 00:47:00 +00:00
"private": true,
"description": "Build tools for the VisualEditor-MediaWiki extension.",
Implement Grunt support (grunt jshint,csslint,qunit,watch) This has no influence on Jenkins but can be used locally to easily run certain tools. Since we already had `.jshintrc` in our repo it was already possible to easily run JSHint from the command-line locally. Taking that as a base the following are new features: * `grunt csslint`: Runs CSSLint on all css files * `grunt qunit`: Runs QUnit (standalone) tests in PhantomJS * `grunt test`: Runs jshint/csslint/qunit * `grunt watch`: Runs the "test" command automatically whenever a file is changed. You can keep this in the background so whenever you save a file in your editor (e.g. Sublime Text) it'll run the tests and if there is a failure, it'll throw a bash error code causing your Terminal application to beep you in whatever way your operating system does so (e.g. for Mac OS X a red badge + jumping icon in the Dock). It will continue to run in the background even after a failure so no need to re-start watch after a failure. * `grunt`: Runs the default task, which is 'test'. Previously to use `jshint .` you had to: * One-time install: * install package -- nodejs npm * npm install -g jshint * Usage: * cd VisualEditor; jshint . Now, for grunt: * One-time install: * install package -- nodejs npm * npm install -g grunt-cli * cd VisualEditor; npm install * Usage: * cd VisualEditor; grunt Change-Id: I7a4fdf4b6bf3f00cef15dc3e2c81eceb595aec7c
2013-05-31 02:33:12 +00:00
"scripts": {
build: Move pre/post 'doc' task into package.json Standard entry point. Change-Id: Ic6cdc9ac1b266a64dcb1522ac36132c5ef844d3c
2015-04-03 09:33:22 +00:00
"test": "grunt test",
"doc": "jsduck",
"postdoc": "grunt copy:jsduck"
Implement Grunt support (grunt jshint,csslint,qunit,watch) This has no influence on Jenkins but can be used locally to easily run certain tools. Since we already had `.jshintrc` in our repo it was already possible to easily run JSHint from the command-line locally. Taking that as a base the following are new features: * `grunt csslint`: Runs CSSLint on all css files * `grunt qunit`: Runs QUnit (standalone) tests in PhantomJS * `grunt test`: Runs jshint/csslint/qunit * `grunt watch`: Runs the "test" command automatically whenever a file is changed. You can keep this in the background so whenever you save a file in your editor (e.g. Sublime Text) it'll run the tests and if there is a failure, it'll throw a bash error code causing your Terminal application to beep you in whatever way your operating system does so (e.g. for Mac OS X a red badge + jumping icon in the Dock). It will continue to run in the background even after a failure so no need to re-start watch after a failure. * `grunt`: Runs the default task, which is 'test'. Previously to use `jshint .` you had to: * One-time install: * install package -- nodejs npm * npm install -g jshint * Usage: * cd VisualEditor; jshint . Now, for grunt: * One-time install: * install package -- nodejs npm * npm install -g grunt-cli * cd VisualEditor; npm install * Usage: * cd VisualEditor; grunt Change-Id: I7a4fdf4b6bf3f00cef15dc3e2c81eceb595aec7c
2013-05-31 02:33:12 +00:00
},
"devDependencies": {
build: Bump miscellaneous devDependencies to latest Updates: * grunt 0.4.2 -> 0.4.5 * grunt-banana-checker 0.1.0 -> 0.2.0 * grunt-contrib-csslint 0.2.0 -> 0.3.1 * grunt-jscs 0.6.1 -> 0.7.1 Change-Id: If1d612cd4ad9b45b0d249931339882f4bc238c74
2014-09-14 06:40:06 +00:00
"grunt": "0.4.5",
build: Declare grunt-cli dependency Change-Id: I6a7fafa3c6e40d2407f07c514167ab9fc7661685
2015-04-03 09:33:50 +00:00
"grunt-cli": "0.1.13",
build: Bump various devDeps to latest and make pass * grunt-contrib-jshint: 0.11.3 -> 0.12.0 This version of the linter cleans up a number of options. 'es5' is now assumed to be true by default, and replaced as 'esversion'; 'latedef' is extended to also cover functions' defintions, disabled for us for now; 'futurehostile' is introduced to aid future-incompatible names for ES6+ support. I adjusted ve.init.mw.DesktopArticleTarget.init.js based on this, as this file is meant to be loaded by all JS-capable clients to determine if it is (amongst other things) capable of ES5, so now we assert ES3 compatibility via jshint. * grunt-jscs: 2.5.0 -> 2.7.0 Minor version bump that doesn't affect us. * grunt-jsonlint: 1.0.6 -> 1.0.7 Trivial version bump that doesn't affect us. Change-Id: Ieb7b6748b0cecf275cfc284fc66617189372461f
2016-02-08 03:37:51 +00:00
"grunt-jsonlint": "1.0.7",
build: Updating development dependencies * grunt-banana-checker: 0.3.0 → 0.4.0 Change-Id: I35ed93e20da10717e232cfbaa27453500adc6dba
2015-10-11 16:06:33 +00:00
"grunt-banana-checker": "0.4.0",
build: Update various devDependencies to latest * grunt-contrib-copy : 0.8.0 -> 0.8.2 * grunt-jsonlint : 1.0.4 -> 1.0.6 * grunt-jscs : 2.1.0 -> 2.5.0 Change-Id: Ia66996d4ccf48bb8baab792fda5cd67863b31575
2015-12-11 20:59:17 +00:00
"grunt-contrib-copy": "0.8.2",
build: Update CSSLint from 0.4.0 to 0.5.0 Change-Id: Ide9d1ac96a9b1eb94b0c01ef8e8665ab75aa00a8
2015-09-18 16:46:36 +00:00
"grunt-contrib-csslint": "0.5.0",
build: Bump various devDeps to latest and make pass * grunt-contrib-jshint: 0.11.3 -> 0.12.0 This version of the linter cleans up a number of options. 'es5' is now assumed to be true by default, and replaced as 'esversion'; 'latedef' is extended to also cover functions' defintions, disabled for us for now; 'futurehostile' is introduced to aid future-incompatible names for ES6+ support. I adjusted ve.init.mw.DesktopArticleTarget.init.js based on this, as this file is meant to be loaded by all JS-capable clients to determine if it is (amongst other things) capable of ES5, so now we assert ES3 compatibility via jshint. * grunt-jscs: 2.5.0 -> 2.7.0 Minor version bump that doesn't affect us. * grunt-jsonlint: 1.0.6 -> 1.0.7 Trivial version bump that doesn't affect us. Change-Id: Ieb7b6748b0cecf275cfc284fc66617189372461f
2016-02-08 03:37:51 +00:00
"grunt-contrib-jshint": "0.12.0",
build: Update jscs and jshint jshint: * Update to grunt-contrib-jshint v0.10.0 (jshint v2.5.0). * Remove coding style options covered by jscs. * Enable new option "freeze" (prohibits changing native prototypes). http://www.jshint.com/blog/new-in-jshint-oct-2013/#option-freeze * Re-order to match http://www.jshint.com/docs/options/ jscs: * Update to grunt-jscs-checker v0.4.4 (jscs v1.4.5). * Format .jscsrc file in a more spacious way and order the properties less arbitrarily (using the jscs's readme order). * Enforce more details of our coding style * Get rid of the unsable "sticky" operator rules which have been deprecated in favour of using other rules instead that are able to enforce this more accurately. - disallowLeftStickedOperators: Remove deprecated rule. * Ternary covered by requireSpacesInConditionalExpression. * Rest covered by requireSpace{Before,After}BinaryOperators. - requireLeftStickedOperators: Remove deprecated rule. * Comma covered by disallowSpaceBeforeBinaryOperators. - requireRightStickedOperators: Remove deprecated rule. * Logical not (!) covered by disallowSpaceAfterPrefixUnaryOperators. See also If46b94ce1, Ib731f11b1 and I0b0cadbc5 in oojs/core. Also: * Update grunt-contrib-watch to latest upstream version. Change log at https://github.com/gruntjs/grunt-contrib-watch/blob/v0.6.1/CHANGELOG#L1-L17 Change-Id: I6c5a34afea8b05a3dca617897c192594df06ca90
2014-05-15 16:12:43 +00:00
"grunt-contrib-watch": "0.6.1",
build: Bump various devDeps to latest and make pass * grunt-contrib-jshint: 0.11.3 -> 0.12.0 This version of the linter cleans up a number of options. 'es5' is now assumed to be true by default, and replaced as 'esversion'; 'latedef' is extended to also cover functions' defintions, disabled for us for now; 'futurehostile' is introduced to aid future-incompatible names for ES6+ support. I adjusted ve.init.mw.DesktopArticleTarget.init.js based on this, as this file is meant to be loaded by all JS-capable clients to determine if it is (amongst other things) capable of ES5, so now we assert ES3 compatibility via jshint. * grunt-jscs: 2.5.0 -> 2.7.0 Minor version bump that doesn't affect us. * grunt-jsonlint: 1.0.6 -> 1.0.7 Trivial version bump that doesn't affect us. Change-Id: Ieb7b6748b0cecf275cfc284fc66617189372461f
2016-02-08 03:37:51 +00:00
"grunt-jscs": "2.7.0",
build: Add grunt-tyops Change-Id: Idb30814e69356eb2b3282fae018c142295df922f
2015-12-09 00:44:55 +00:00
"grunt-tyops": "0.1.0"
Implement Grunt support (grunt jshint,csslint,qunit,watch) This has no influence on Jenkins but can be used locally to easily run certain tools. Since we already had `.jshintrc` in our repo it was already possible to easily run JSHint from the command-line locally. Taking that as a base the following are new features: * `grunt csslint`: Runs CSSLint on all css files * `grunt qunit`: Runs QUnit (standalone) tests in PhantomJS * `grunt test`: Runs jshint/csslint/qunit * `grunt watch`: Runs the "test" command automatically whenever a file is changed. You can keep this in the background so whenever you save a file in your editor (e.g. Sublime Text) it'll run the tests and if there is a failure, it'll throw a bash error code causing your Terminal application to beep you in whatever way your operating system does so (e.g. for Mac OS X a red badge + jumping icon in the Dock). It will continue to run in the background even after a failure so no need to re-start watch after a failure. * `grunt`: Runs the default task, which is 'test'. Previously to use `jshint .` you had to: * One-time install: * install package -- nodejs npm * npm install -g jshint * Usage: * cd VisualEditor; jshint . Now, for grunt: * One-time install: * install package -- nodejs npm * npm install -g grunt-cli * cd VisualEditor; npm install * Usage: * cd VisualEditor; grunt Change-Id: I7a4fdf4b6bf3f00cef15dc3e2c81eceb595aec7c
2013-05-31 02:33:12 +00:00
}
}
Reference in a new issue Copy permalink