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

{
  "name": "visualeditor",
  "version": "0.0.0",
  "scripts": {
    "test": "grunt test"
  },
  "repository": {
    "type": "git",
    "url": "https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git"
  },
  "licenses": [
    {
      "type": "MIT",
      "url": "https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor.git/master/LICENSE.txt"
    }
  ],
  "devDependencies": {
    "grunt": "0.4.2",
    "grunt-contrib-csslint": "0.2.0",
    "grunt-contrib-jshint": "0.10.0",
    "grunt-contrib-watch": "0.6.1",
    "grunt-banana-checker": "0.1.0",
    "grunt-jscs-checker": "0.6.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",`
			`"scripts": {`
			`"test": "grunt test"`
			`},`
			`"repository": {`
			`"type": "git",`
			`"url": "https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git"`
			`},`
			`"licenses": [`
			`{`
			`"type": "MIT",`
Updates to README.md and CODING.md Describe how to report bugs, install grunt, and run tests. Update jsduck instructions. Fix path to license file in package.json. Change-Id: I276ff0ea4324f027dafc044a86fa564b2439089a 2013-08-27 16:13:43 +00:00			`"url": "https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FVisualEditor.git/master/LICENSE.txt"`
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": {`
Set up node-jscs, pass it, and configure in local Gruntfile Let's experiment with this via our local Gruntfile. If it works fine we can install it in Jenkins (similar to node-csslint). Verify through $ npm install && npm test; Fixed all outstanding violations. Also: * Added syntaxhighight to ignore. * Added imetests (which contain unformatted JSON) to ignore. * In ve.dm.ModelRegistry#matchTypeRegExps, removed redundant !! cast from the [+!!withFunc] statement which was hitting a bug in node-jscs. All callers to this local private function pass a literal boolean true/false so no need to cast it. * Removed "/* key .. , value /" from ve.setProp, though this wasn't caught by node-jscs, found it when searching for " , ". Made npm.devDependencies fixed instead of using tilde-ranges. This too often leads to strange bugs or sudden changes. Fixed them at the version they were currently ranging to. Bug: 54218 Change-Id: Ib2630806f3946874c8b01e58cf171df83a28da29 2013-12-06 02:34:44 +00:00			`"grunt": "0.4.2",`
grunt: Update devDependencies Change-Id: I0076d07e2029039283984dd2ae0b0e775b3e00c0 2013-12-18 07:18:43 +00:00			`"grunt-contrib-csslint": "0.2.0",`
Grunt: Clean up * Use jshintrc:true which lets grunt defer autodiscovery of the file to jshint instead of forcing it to '.jshintrc'. This allows us to override certain settings from a subdirectory, to match behaviour of standalone jshint. * Sort modules. * Use plain string instead of single-value array. Change-Id: Ib5cd48f3ff0367b8fc84627c29e4fb32452087c0 2014-06-04 03:07:12 +00:00			`"grunt-contrib-jshint": "0.10.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",`
Use new banana checker as a linter to avoid lacking qqq messages Change-Id: I02647d519ff85f78178d4fb48f014081ca3e82ef 2014-04-04 22:22:57 +00:00			`"grunt-banana-checker": "0.1.0",`
build: Update jscs and use new "wikimedia" preset Our coding style has been upstreamed and first released in node-jscs v1.5.0 (grunt-jscs-checker v0.6.0). Change-Id: Ifc0cfc7177946b9d11407f60e38b0177883724c5 2014-06-26 10:41:18 +00:00			`"grunt-jscs-checker": "0.6.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			`}`
			`}`