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",
		"screenshots-all": "grunt screenshots-all"
	},
	"devDependencies": {
		"eslint-config-wikimedia": "0.10.0",
		"grunt": "1.0.3",
		"grunt-banana-checker": "0.6.0",
		"grunt-contrib-copy": "1.0.0",
		"grunt-contrib-watch": "1.1.0",
		"grunt-eslint": "21.0.0",
		"grunt-image": "4.2.0",
		"grunt-jsonlint": "1.1.0",
		"grunt-mocha-test": "0.13.3",
		"grunt-stylelint": "0.10.1",
		"grunt-tyops": "0.1.0",
		"jimp": "0.5.0",
		"mocha": "5.2.0",
		"selenium-webdriver": "3.6.0",
		"stringify-object": "3.2.2",
		"stylelint-config-wikimedia": "0.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			`{`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`"name": "visualeditor",`
			`"version": "0.0.0",`
			`"private": true,`
			`"description": "Build tools for the VisualEditor-MediaWiki extension.",`
			`"scripts": {`
			`"test": "grunt test",`
			`"doc": "jsduck",`
build: npm/rake entry point for screenshots upload We have a Jenkins job to take screenshots of VisualEditor and upload the result to commons.wikimedia.org. That roughly does: npm install node_modules/.bin/grunt screenshots-all bundle install bundle exec upload However on CI, the Docker container only accepts 'npm run-script XXX' or 'bundle exec rake YYY'. Add a npm script 'screenshots-all' invoking 'grunt screenshots-all'. Add a rake task 'commons_upload'. I have added a basic check to make sure environment variables are properly set before invoking the upload script. Thus on CI the usage will become: npm install npm run-script screenshots-all bundle install bundle exec rake commons_upload Which match the CI convention. Bug: T189122 Change-Id: I221ed8d6178dd036eac287f0f811834a6d4ffd22 2018-03-07 14:43:25 +00:00			`"postdoc": "grunt copy:jsduck",`
			`"screenshots-all": "grunt screenshots-all"`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`},`
			`"devDependencies": {`
build: Update eslint-config-wikimedia to 0.10.0 Change-Id: I63a0ebf0b31a0d5d4e680a4e2a5a0be4850be165 2019-01-08 17:00:09 +00:00			`"eslint-config-wikimedia": "0.10.0",`
build: Bump linters for eslint 5 and make pass Change-Id: I88627028e5806c2fdceb76fd26bcb57d44ed4c20 2018-07-05 23:59:22 +00:00			`"grunt": "1.0.3",`
build: Bump a couple of devDependencies to latest grunt-banana-checker 0.5.0 → 0.6.0 grunt-stylelint 0.7.0 → 0.8.0 Added stylelint peerdependency directly. Change-Id: Ib5da82ae60f4f49e572459c8e53f9125ad422ee8 2017-07-06 20:39:50 +00:00			`"grunt-banana-checker": "0.6.0",`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`"grunt-contrib-copy": "1.0.0",`
build: Bump linters for eslint 5 and make pass Change-Id: I88627028e5806c2fdceb76fd26bcb57d44ed4c20 2018-07-05 23:59:22 +00:00			`"grunt-contrib-watch": "1.1.0",`
			`"grunt-eslint": "21.0.0",`
build: Bump some devDependencies to latest grunt 1.0.1 → 1.0.2 grunt-contrib-watch 1.0.0 → 1.0.1 grunt-image 4.1.0 → 4.2.0 grunt-stylelint 0.9.0 → 0.10.0 stylelint 8.2.0 → 9.2.0 stylelint-config-wikimedia 0.4.2 → 0.4.3 Leaving babel-polyfill, grunt-mocha-test, jimp, mocha and selenium-webdriver alone for now. Change-Id: Ibea983670108a56ddbf748e140831147e31da329 2018-04-25 19:35:07 +00:00			`"grunt-image": "4.2.0",`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`"grunt-jsonlint": "1.1.0",`
build: Update devDependencies grunt-mocha-test 0.12.7 → 0.13.3 grunt-stylelint 0.10.0 → 0.10.1 jimp 0.2.28 → 0.5.0 Change-Id: Ic2b1bcefdce6e8f71c623eec877151b7233c9556 2018-09-15 20:45:49 +00:00			`"grunt-mocha-test": "0.13.3",`
			`"grunt-stylelint": "0.10.1",`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`"grunt-tyops": "0.1.0",`
build: Update devDependencies grunt-mocha-test 0.12.7 → 0.13.3 grunt-stylelint 0.10.0 → 0.10.1 jimp 0.2.28 → 0.5.0 Change-Id: Ic2b1bcefdce6e8f71c623eec877151b7233c9556 2018-09-15 20:45:49 +00:00			`"jimp": "0.5.0",`
build: Bump devDependencies related to the screenshots task This fixes a bunch of warnings from `npm audit`. Change-Id: I31321f2f19421944787279923e010f8093789d5e 2018-07-06 17:37:25 +00:00			`"mocha": "5.2.0",`
			`"selenium-webdriver": "3.6.0",`
Update VE core submodule to master (2f27b1a2c) New changes: 2915330a9 Avoid JSON strings in built demo files 62b0b1298 Move server files to /src ddd99ab0c MediaSizeWidget: Add #updateDisabled() for disableable sub-widgets Bug: T204185 Change-Id: Ied5b39608683ba7c9f056430a0a248f41e089d5a 2018-09-25 15:12:56 +00:00			`"stringify-object": "3.2.2",`
build: Upgrade stylelint-config-wikimedia to 0.5.0 and make pass Change-Id: I4c547757ed5a32ff98b1cf2670010db302bd8467 2018-12-03 18:20:02 +00:00			`"stylelint-config-wikimedia": "0.5.0"`
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2 2017-03-31 21:50:07 +00:00			`}`
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			`}`