Change Details

As Readers Web works on the desktop improvements project, we’d like to keep track of the byte sizes of individual ResourceLoader modules inside Vector in order to avoid any performance regressions. We've written a Node script that fetches each ResourceLoader module and runs it through the bundlesize library to validate it’s payload size. https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/602780/ This script depends on a running mediawiki installation as well as the MW_SERVER and MW_SCRIPT_PATH env variables to successfully fetch the modules. We would like to create a job that runs this script in CI on a per-commit basis. It is currently running as the `npm run selenium-test` job, but that might be temporary solution.

As Readers Web works on the desktop improvements project, we’d like to keep track of the byte sizes of individual ResourceLoader modules inside Vector in order to avoid any performance regressions. We've written a Node script that fetches each ResourceLoader module and runs it through the bundlesize library to validate it’s payload size. https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/602780/ This script can be converted to a MediaWikiIntegrationTest.

As Readers Web works on the desktop improvements project, we’d like to keep track of the byte sizes of individual ResourceLoader modules inside Vector in order to avoid any performance regressions. We've written a Node script that fetches each ResourceLoader module and runs it through the bundlesize library to validate it’s payload size. https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Vector/+/602780/ This script depends on a running mediawiki installation as well as the MW_SERVER and MW_SCRIPT_PATH env variables to successfully fetch the modules. We would like to create a job that runs this script in CI on a per-commit basis. It is currently running as the `npm run selenium-test` job, but that might be temporary solution. can be converted to a MediaWikiIntegrationTest.