wikimedia/mediawiki-skins-MinervaNeue
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/skins/MinervaNeue synced 2024-12-18 16:51:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-skins-MinervaNeue/bundlesize.config.json

23 lines
375 B
JSON
Raw Normal View History

Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
[
Add module to bundlesize.config Adding skins.minerva.styles to bundlesize.config.json Bug: T266361 Change-Id: I2ad07a0a8253a7b98651b64aca6a816a90a384e9
2024-11-12 18:13:50 +00:00
{
"resourceModule": "skins.minerva.styles",
Increase bundlesize limits Codex v1.18.0 added 8 new tokens and styles for various components. Refer to changelog for more info: https://github.com/wikimedia/design-codex/blob/main/CHANGELOG.md#1180--2024-12-10 Bug: T381787 Change-Id: I58401027164c50a7eab694789597678e13392561
2024-12-10 23:10:59 +00:00
"maxSize": "10.8KB"
Add module to bundlesize.config Adding skins.minerva.styles to bundlesize.config.json Bug: T266361 Change-Id: I2ad07a0a8253a7b98651b64aca6a816a90a384e9
2024-11-12 18:13:50 +00:00
},
Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
{
"resourceModule": "skins.minerva.content.styles.images",
Add color: var( --color-base ); to .notheme class Adds a rule that makes elements using the .notheme class inherit black text unless specified otherwise. This addresses situations where elements relying on inheritance for color. Bug: T358528 Change-Id: Ie59c31b5e25684ff5ecad507a273fbe71af4bca0
2024-03-07 21:21:37 +00:00
"maxSize": "0.3KB"
Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
},
{
"resourceModule": "mediawiki.hlist",
Add color: var( --color-base ); to .notheme class Adds a rule that makes elements using the .notheme class inherit black text unless specified otherwise. This addresses situations where elements relying on inheritance for color. Bug: T358528 Change-Id: Ie59c31b5e25684ff5ecad507a273fbe71af4bca0
2024-03-07 21:21:37 +00:00
"maxSize": "0.3KB"
Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
},
Merge Icon Style mergeIconStyleModules Merging skins.minerva.icons.wikimedia and skins.minerva.mainMenu.icons modules into skins.minerva.icons Bug: T266361 Change-Id: I4095da5a0c6d2cff8ccd1ff1504a2d54635d1828
2024-11-12 21:43:33 +00:00
{
"resourceModule": "skins.minerva.icons",
"maxSize": "0.6KB"
},
Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
{
"resourceModule": "skins.minerva.scripts",
Increase bundlesize in anticipation of next Codex release The increase is due to the increase in size of the cdx icon mixin. This does not impact render blocking CSS so this is an acceptable change. Bug: T358028 Change-Id: Icea7aa0d2f80f33fc64fd9c7721a371e115a32cb
2024-02-20 22:54:34 +00:00
"maxSize": "14.5KB"
Run bundlesize tests on every commit It was added in 7340485014a7a0dd4a1413367fc9abfc3bcfdd61 but for some reason never enabled. This was supposed to be protecting us from performance regressions by monitoring the size of modules in the repo. It appears to be broken both locally and on Jenkins when run on the due to some changes in Phabricator. Since then we've added bundle size tests to Vector using a different more foolproof method. I think that method is more preferable as it also provides coverage for JS and icons so the associated script is copied over and used in Minerva and activated on all commits. Bug: T259080 Change-Id: I9ba2dcc060ec09d91814c947d5be3f71b055a66e
2020-07-23 18:19:45 +00:00
}
]
Reference in a new issue Copy permalink