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",
    "doc": "jsduck",
    "postdoc": "grunt copy:jsduck"
  },
  "devDependencies": {
    "grunt": "1.0.1",
    "grunt-cli": "1.2.0",
    "grunt-jsonlint": "1.0.7",
    "grunt-banana-checker": "0.5.0",
    "grunt-contrib-copy": "1.0.0",
    "grunt-contrib-csslint": "1.0.0",
    "grunt-contrib-jshint": "1.0.0",
    "grunt-contrib-watch": "1.0.0",
    "grunt-jscs": "2.8.0",
    "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			`{`
			`"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 various devDependencies to latest grunt 0.4.5 → 1.0.1 grunt-cli 0.1.13 → 1.2.0 grunt-banana-checker 0.4.0 → 0.5.0 Change-Id: Idcd66807d03c85005ca97f5563251e814d15813b 2016-04-12 18:00:29 +00:00			`"grunt": "1.0.1",`
			`"grunt-cli": "1.2.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-jsonlint": "1.0.7",`
build: Bump various devDependencies to latest grunt 0.4.5 → 1.0.1 grunt-cli 0.1.13 → 1.2.0 grunt-banana-checker 0.4.0 → 0.5.0 Change-Id: Idcd66807d03c85005ca97f5563251e814d15813b 2016-04-12 18:00:29 +00:00			`"grunt-banana-checker": "0.5.0",`
build: Bump all devDependencies to latest * grunt-contrib-copy: 0.8.2 -> 1.0.0 * grunt-contrib-csslint: 0.5.0 -> 1.0.0 * grunt-contrib-jshint: 0.12.0 -> 1.0.0 * grunt-jscs: 2.7.0 -> 2.8.0 Change-Id: I8c4b3e1ad4e10217e9e048eacd8dedc8fe5caf02 2016-03-10 16:19:48 +00:00			`"grunt-contrib-copy": "1.0.0",`
			`"grunt-contrib-csslint": "1.0.0",`
			`"grunt-contrib-jshint": "1.0.0",`
build: Bump devDependencies to latest grunt-contrib-watch 0.6.1 → 1.0.0 Change-Id: Ieea149cd930e470ec7f63e7c5cc75aef60a5a271 2016-03-17 19:42:38 +00:00			`"grunt-contrib-watch": "1.0.0",`
build: Bump all devDependencies to latest * grunt-contrib-copy: 0.8.2 -> 1.0.0 * grunt-contrib-csslint: 0.5.0 -> 1.0.0 * grunt-contrib-jshint: 0.12.0 -> 1.0.0 * grunt-jscs: 2.7.0 -> 2.8.0 Change-Id: I8c4b3e1ad4e10217e9e048eacd8dedc8fe5caf02 2016-03-10 16:19:48 +00:00			`"grunt-jscs": "2.8.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			`}`
			`}`