wikimedia/mediawiki-extensions-Popups
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/Popups synced 2024-11-12 09:18:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Popups/package.json

37 lines
1.4 KiB
JSON
Raw Normal View History

build: Configure banana-checker and jsonlint Change-Id: Id3f1d601f6b99e9646c7a1c6b430b1dd777e952b
2015-06-20 05:09:03 +00:00
{
"private": true,
"scripts": {
Tooling: Add npm start script for development mode Run webpack in watch mode for development. Scripts are documented in a followup commit in the README. Change-Id: Id1e2f8b8578169eee53a5e4f8c468d5426d4c2ea
2017-02-13 13:27:20 +00:00
"start": "webpack -w",
Enable production settings for the production bundle It enables certain optimizations, see: * https://webpack.js.org/guides/production-build/ Code is minified by uglifyjs. Aditional changes: * Add banner so that sources are not minified by ResourceLoader Bug: T160061 Change-Id: I50c9148ebf2d860db42a24225bc128bfcfe56927
2017-05-08 18:50:59 +00:00
"build": "NODE_ENV=production webpack",
Test: Upgrade mw-node-qunit and use globs To get cross-shell and OS glob support and fix some of the sinon deprecation warnings regarding getConfig. Bug: T168054 Change-Id: Idd6d47c1e63836c8429156cd9030ef9fda4479b1
2017-06-16 12:12:26 +00:00
"test:node": "mw-node-qunit 'tests/node-qunit/**/*.js' | tap-dot",
Tools: Add pre-commit git hook to auto test and build That way before commits it will run tests and add compiled sources automatically removing some of the pain of having to commit the compiled assets for now. Additional changes: * Extract npm test:dev from npm test to run lint and tests without the CI check (to be re-used in the pre-commit hook) Bug: T160061 Change-Id: I6e1201ef7dae5fef34b14cabc0292fb1aa4e5997
2017-05-10 17:58:07 +00:00
"test:dev": "grunt lint && npm run test:node",
Run doc generation on `npm test` The benefit of this is if there are any problems with the documentation they will not enter our codebase. We do a similar thing in MobileFrontend Bug: T158236 Change-Id: I30329dd868fe596c490f95354c3226c9cd4a2fc7
2017-05-26 17:26:35 +00:00
"test": " npm run check-built-assets && npm run test:dev && npm run doc",
doc: Replace JSDuck v5.3.4 with JSDoc v3.4.3 JSDoc can handle ES2015 modules whereas JSDuck can't. Regardless of however many features JSDuck has that JSDoc mightn't [0], we can't use JSDuck to document this codebase. [0] T138401 Bug: T158236 Change-Id: I8da712075dd28f6b228c96fa9577ca39eb148fb5
2017-05-19 11:28:35 +00:00
"doc": "jsdoc -c jsdoc.json",
doc: Add doc:start script Like npm run start, npm run doc:start will rebuild the documentation if any file in the src directory changes. Supporting changes: * Use nodemon@1.11.0. Change-Id: I7b528525874e377533e92c0a80c8aae9f6a18620
2017-05-25 11:27:43 +00:00
"doc:start": "nodemon --watch src --exec 'npm run doc'",
Tooling: Make diffing in check-built-assets verbose So that it is easier to diagnose what the differences are between the commited built files and the ones compiled for the check. Change-Id: Id5394bda910c8218123a87d4604351fe5ae95d1e
2017-03-02 15:17:01 +00:00
"check-built-assets": "echo 'CHECKING BUILD SOURCES ARE COMMITED' && rm -rf test-build && mv resources/dist test-build && npm run build && diff -x '*.map' -r test-build resources/dist && rm -rf test-build",
Tools: Add pre-commit git hook to auto test and build That way before commits it will run tests and add compiled sources automatically removing some of the pain of having to commit the compiled assets for now. Additional changes: * Extract npm test:dev from npm test to run lint and tests without the CI check (to be re-used in the pre-commit hook) Bug: T160061 Change-Id: I6e1201ef7dae5fef34b14cabc0292fb1aa4e5997
2017-05-10 17:58:07 +00:00
"coverage": "istanbul cover node_modules/.bin/mw-node-qunit tests/node-qunit/*.js tests/node-qunit/**/*.js",
"precommit": "npm run test:dev && npm run build && git add resources/dist"
build: Configure banana-checker and jsonlint Change-Id: Id3f1d601f6b99e9646c7a1c6b430b1dd777e952b
2015-06-20 05:09:03 +00:00
},
"devDependencies": {
build: Update eslint to 0.4.0 and make pass Change-Id: I7d301049f0c91f79e82f996b2dce770840c27e72
2017-05-04 20:55:59 +00:00
"eslint-config-wikimedia": "0.4.0",
Remove jshint/jscs, add eslint and stylelint ...with the wikimedia presets. For automatically fixing most of the JS lint problems run grunt eslint:fix Some rules of stylelint were disabled given they cause problems with existing popups code (like no id selectors for example). Change-Id: I2153047c3ddbea50572dd329989088bb20787515
2016-12-16 11:11:54 +00:00
"grunt": "1.0.1",
"grunt-banana-checker": "0.5.0",
"grunt-cli": "^1.2.0",
Update linting and enable command line QUnit You can use `grunt watch` now! Changes: * Re-enable QUnit (but ignore legacy tests) * Add a sample QUnit test * Add ability to run QUnit via `grunt watch` or `grunt test` * Move linting to `grunt lint` task * Add Redux to globals in linter Change-Id: Ie4a65a8a66773d6472b3d73257267d18027ff3c3
2016-11-08 15:59:22 +00:00
"grunt-contrib-watch": "^1.0.0",
Remove jshint/jscs, add eslint and stylelint ...with the wikimedia presets. For automatically fixing most of the JS lint problems run grunt eslint:fix Some rules of stylelint were disabled given they cause problems with existing popups code (like no id selectors for example). Change-Id: I2153047c3ddbea50572dd329989088bb20787515
2016-12-16 11:11:54 +00:00
"grunt-eslint": "19.0.0",
"grunt-jsonlint": "1.1.0",
"grunt-stylelint": "^0.6.0",
Tools: Add pre-commit git hook to auto test and build That way before commits it will run tests and add compiled sources automatically removing some of the pain of having to commit the compiled assets for now. Additional changes: * Extract npm test:dev from npm test to run lint and tests without the CI check (to be re-used in the pre-commit hook) Bug: T160061 Change-Id: I6e1201ef7dae5fef34b14cabc0292fb1aa4e5997
2017-05-10 17:58:07 +00:00
"husky": "^0.13.3",
Add code coverage reports npm script Generate code coverage reports based on the node-qunit tests with istanbul. Changes: * Update README with npm run coverage * Add .istanbul.yml to configure istanbul * Add npm script "coverage" that runs istanbul and generates the reports Example report: http://popups-coverage.surge.sh/lcov-report/index.html Change-Id: I9be8c04b858a3ce6f4e29af2685b79253e3b4dca
2017-03-03 12:34:33 +00:00
"istanbul": "^0.4.5",
doc: Replace JSDuck v5.3.4 with JSDoc v3.4.3 JSDoc can handle ES2015 modules whereas JSDuck can't. Regardless of however many features JSDuck has that JSDoc mightn't [0], we can't use JSDuck to document this codebase. [0] T138401 Bug: T158236 Change-Id: I8da712075dd28f6b228c96fa9577ca39eb148fb5
2017-05-19 11:28:35 +00:00
"jsdoc": "^3.4.3",
Tests: Up the min version of the node qunit runner It has important improvements, and we don't want dev to use a previous version. List of changes on the runner: * 1.0.6 Add globals to window too * 1.0.5 Don't reorder or run tests in parallel * 1.0.4 Don't autostart the tests, they are manually started * 1.0.3 Invoke sandbox restore after hooks have been called * 1.0.2 Default fake timers and server to false See https://github.com/joakin/mw-node-qunit/commits/master Change-Id: Ic3283c99eb374bc9f85c703ef0b55f875d527e0b
2017-02-22 11:10:42 +00:00
"mock-require": "^2.0.1",
Test: Upgrade mw-node-qunit and use globs To get cross-shell and OS glob support and fix some of the sinon deprecation warnings regarding getConfig. Bug: T168054 Change-Id: Idd6d47c1e63836c8429156cd9030ef9fda4479b1
2017-06-16 12:12:26 +00:00
"mw-node-qunit": "^2.1.0",
doc: Add doc:start script Like npm run start, npm run doc:start will rebuild the documentation if any file in the src directory changes. Supporting changes: * Use nodemon@1.11.0. Change-Id: I7b528525874e377533e92c0a80c8aae9f6a18620
2017-05-25 11:27:43 +00:00
"nodemon": "^1.11.0",
Redux and redux-thunk now packaged inside ext.popups Until this appears in core it makes sense to package it up as part of ext.popups resource loader module. Version numbers from npm are pinned to exact versions to control the upgrade path of the libraries instead of leaving it to semver on developers machines. Bug: T156333 Change-Id: I33368ecc3c8e911d96f846669bcd831c182749f2
2017-02-02 22:49:42 +00:00
"redux": "3.6.0",
"redux-thunk": "2.2.0",
build: Update stylelint to 0.4.1 Change-Id: I143662a36bf5d79cfc5b35ec62c3473f91afd14c
2017-03-20 14:41:14 +00:00
"stylelint-config-wikimedia": "0.4.1",
Set up qunit running in node to migrate tests to commonjs In order to run qunit tests on sources that use common.js modules, set up infra to run qunit tests in the node cli when running: npm run test:node Changes: * Add npm script test:node that runs the tests * Run node tests on CI (npm test) * Add a qunit node test runner: mw-node-qunit * Migrate a test from the root hierarchy and another one from the nested one to prove it works (globs fail otherwise) * reducers/settings.test.js to node qunit to prove it works * counts.test.js to node qunit to prove it works Change-Id: I55d76b7db168f3745e0ac69852c152322ab385c3
2017-02-01 11:09:42 +00:00
"tap-dot": "^1.0.5",
Tools: Upgrade webpack to 2.6 To benefit from the bugfixes See https://github.com/webpack/webpack/releases Change-Id: Ia4a10c821d6dc4257bfea57658cf16d1ac028bf4
2017-05-23 18:28:23 +00:00
"webpack": "^2.6.0"
build: Configure banana-checker and jsonlint Change-Id: Id3f1d601f6b99e9646c7a1c6b430b1dd777e952b
2015-06-20 05:09:03 +00:00
}
}
Reference in a new issue Copy permalink