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

30 lines
755 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
{
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.17.0 Fix instances of variable shadowing. Change-Id: I6e2befb020d7d4b506c7b46131eafacd951aa6d1
2020-08-18 12:16:49 +00:00
"eslint-config-wikimedia": "0.17.0",
build: Updating grunt to 1.3.0 Change-Id: I9cda32285abdd0d9a06e0defa8da488b400e66a9
2020-08-30 21:48:44 +00:00
"grunt": "1.3.0",
build: Updating npm dependencies * eslint-config-wikimedia: 0.15.0 → 0.15.3 The following rules are failing and were disabled: * mediawiki/class-doc * mediawiki/valid-package-file-require * grunt-banana-checker: 0.8.1 → 0.9.0 * grunt-stylelint: 0.14.0 → 0.15.0 * stylelint-config-wikimedia: 0.9.0 → 0.10.1 Change-Id: If718fe8876cc4721602757d38fe06ab421ce8d80
2020-04-16 22:55:04 +00:00
"grunt-banana-checker": "0.9.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",
build: Update eslint-config-wikimedia to 0.16.0 Change-Id: I638e0f82949597e2a2e4ea18fc2f0258f225358c
2020-06-02 20:30:00 +00:00
"grunt-eslint": "23.0.0",
build: Upgrade stylelint-config-wikimedia from 0.5.0 to 0.6.0 Additionally a bump to grunt-image and grunt itself for security reasons. Also, commit package-lock.json, which is what we do now. Change-Id: I2beab15d7f5b1453ccbb3c46b6dd0800c78ed15b
2019-06-26 21:09:49 +00:00
"grunt-image": "5.0.1",
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",
build: Updating npm dependencies * eslint-config-wikimedia: 0.15.0 → 0.15.3 The following rules are failing and were disabled: * mediawiki/class-doc * mediawiki/valid-package-file-require * grunt-banana-checker: 0.8.1 → 0.9.0 * grunt-stylelint: 0.14.0 → 0.15.0 * stylelint-config-wikimedia: 0.9.0 → 0.10.1 Change-Id: If718fe8876cc4721602757d38fe06ab421ce8d80
2020-04-16 22:55:04 +00:00
"grunt-stylelint": "0.15.0",
Use tabs to indent in json Change-Id: Ib0372c86bcaac368f4dd68a512273b504ca9b6b2
2017-03-31 21:50:07 +00:00
"grunt-tyops": "0.1.0",
screenshots: Update jimp Change-Id: I32f663219f9c907d90329b198b962763a6a6a96b
2020-06-26 11:33:23 +00:00
"jimp": "0.13.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: Updating npm dependencies * eslint-config-wikimedia: 0.15.0 → 0.15.3 The following rules are failing and were disabled: * mediawiki/class-doc * mediawiki/valid-package-file-require * grunt-banana-checker: 0.8.1 → 0.9.0 * grunt-stylelint: 0.14.0 → 0.15.0 * stylelint-config-wikimedia: 0.9.0 → 0.10.1 Change-Id: If718fe8876cc4721602757d38fe06ab421ce8d80
2020-04-16 22:55:04 +00:00
"stylelint-config-wikimedia": "0.10.1"
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
}
Reference in a new issue Copy permalink