wikimedia/mediawiki-skins-MinervaNeue
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/skins/MinervaNeue synced 2024-11-27 23:50:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-skins-MinervaNeue/bundlesize.config.json

31 lines
548 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
[
{
"resourceModule": "skins.minerva.base.styles",
Convert all color related Less variables to CSS custom properties All colors used in Minerva are converted from Less variables into CSS custom properties. A new file called CSSCustomProperties.less is created in the skins.minerva.base.styles module to store these custom properties and an ADR is provided on the rationale for dropping support for browsers that don't support custom properties. The new CSS custom properties follow Codex design token conventions where possible (and noted when not). Link colors are unique because their styles are defined in core, so in that case the Less variables values are set to custom properties. Those values are then fed back into MediaWiki core for core link styling. Also adds a temporary night-mode color palette under the .skin-nightmode-1 class on the <html> element. Bug: T356074 Change-Id: Ida1f14138f12bd3c600c264bde7b5100f9dbf4ff
2024-02-01 17:33:08 +00:00
"maxSize": "8KB"
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",
"maxSize": "0.5KB"
},
{
"resourceModule": "mediawiki.hlist",
"maxSize": "0.5KB"
},
{
"resourceModule": "skins.minerva.icons.wikimedia",
Fix last modified bar icon change and search unStar-progressive In b4fd1498bc we set a variant, which dropped the default global progressive and invert variants. This is turn, made the mobile watchstar on search disappear when selected. Here we restore those icon variants, and take the time to refactor the code so its more resilient against future icon changes. Change-Id: I1423fbf69dce87715c159877b5f536b4e8e13390
2021-11-01 21:00:19 +00:00
"maxSize": "1.0KB"
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.mainMenu.icons",
"maxSize": "0.4KB"
},
{
"resourceModule": "skins.minerva.mainMenu.styles",
"maxSize": "1.2KB"
},
{
"resourceModule": "skins.minerva.scripts",
Drop mw.mobileFrontend references This restores the previously reverted patchset If5b76245bf60bfa9cf977cdbf37ee0d6bb65f9d9 Changes since original: * Added Depends-On to MobileFrontend * Uses OOUI classes for page issues rather than es6 classes - ES6 classes do not support modifications to class prior to running super so MobileFrontend's View class is not compatible without significant refactors. Depends-On: I24ad75adf8519102ca356d64d99d765ab69180cc Bug: T348807 Change-Id: I4ff82af0251254c846f2caee330af5af738f6029
2023-11-07 16:29:17 +00:00
"maxSize": "12.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
}
]
Reference in a new issue Copy permalink