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

25 lines
632 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: Replace csslint with stylelint For now just use the rules file in lib/ve, but eventually this will be a preset. Change-Id: I7fd79d3e1dce37aef066d416cd969e5fff1e962f Depends-On: I17e0d23ddfedf64985495ab35d113ea08c03b1df
2016-05-16 14:38:57 +00:00
"babel-polyfill": "6.8.0",
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-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-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: Replace csslint with stylelint For now just use the rules file in lib/ve, but eventually this will be a preset. Change-Id: I7fd79d3e1dce37aef066d416cd969e5fff1e962f Depends-On: I17e0d23ddfedf64985495ab35d113ea08c03b1df
2016-05-16 14:38:57 +00:00
"grunt-jsonlint": "1.0.7",
build: Bump grunt-stylelint to v0.3.0 Change-Id: I8e6eb487a1ae181c9279aaf2c0aec5cccc8d9427
2016-05-19 18:04:10 +00:00
"grunt-stylelint": "0.3.0",
build: Replace csslint with stylelint For now just use the rules file in lib/ve, but eventually this will be a preset. Change-Id: I7fd79d3e1dce37aef066d416cd969e5fff1e962f Depends-On: I17e0d23ddfedf64985495ab35d113ea08c03b1df
2016-05-16 14:38:57 +00:00
"grunt-tyops": "0.1.0",
Update stylelint config version and make a pass Change-Id: I58007c3976019c8cfe96fd1fc0474d9e80f99f64
2016-05-24 12:41:13 +00:00
"stylelint-config-wikimedia": "0.2.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