mediawiki-extensions-Visual.../package.json

{
  "name": "visualeditor",
  "version": "0.0.0",
  "private": true,
  "description": "Build tools for the VisualEditor-MediaWiki extension.",
  "scripts": {
    "test": "grunt test"
  },
  "devDependencies": {
    "grunt": "0.4.5",
    "grunt-banana-checker": "0.2.1",
    "grunt-contrib-csslint": "0.4.0",
    "grunt-contrib-jshint": "0.11.0",
    "grunt-contrib-watch": "0.6.1",
    "grunt-jscs": "1.5.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			`{`
			`"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": {`
			`"test": "grunt test"`
			`},`
			`"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: Update grunt-banana-checker to v0.2.1 Change-Id: If3954c2a01117df036ffe89df2f37044a32f6a41 2015-03-27 23:41:56 +00:00			`"grunt-banana-checker": "0.2.1",`
build: Bump devDependencies to latest Updates: * grunt-contrib-csslint 0.3.1 -> 0.4.0 * grunt-contrib-jslint 0.10.0 -> 0.11.0 * grunt-jscs 0.8.1 -> 1.2.0 For jscs, leaving requireSpacesInsideArrayBrackets to avoid headaches for now. Change-Id: I62d34444edbba65c8bd22d2fa5e50e16cabb0042 2015-01-31 00:41:37 +00:00			`"grunt-contrib-csslint": "0.4.0",`
			`"grunt-contrib-jshint": "0.11.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: Update jscs to latest Change-Id: Ic1193d5557e0a3468c16896767888e8a593671e0 2015-03-06 00:01:47 +00:00			`"grunt-jscs": "1.5.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			`}`
			`}`