Conversation
Pull Request Test Coverage Report for Build 23184849248Details
💛 - Coveralls |
|
The only super weird thing I noticed is that the built version shows weird icons, seems like them are bigger and bolder ?? Kooha-2026-03-17-08-26-08.webm |
Vite 8's Rolldown bundler reorders CSS chunks in production, reversing
the cascade order for auto-imported component styles vs statically
imported CSS. This caused Material Design Icons to appear bigger and
bolder in production builds (`.material-icons{font-size:24px}` winning
over `.v-icon--size-default{font-size:1.5em}`).
Wrap the material-design-icons-iconfont import in a CSS `@layer` so
Vuetify's unlayered component styles always take precedence regardless
of source order.
Ref: vitejs/vite#21903
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The icon font rendering issue (icons appearing bigger/bolder in production builds) was caused by Vite 8's Rolldown bundler reordering CSS chunks, reversing the cascade between dev and production modes. Reported upstream: vitejs/vite#21903 Workaround applied in b0607f8: wrap the |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
This pull-request is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this pull-request entirely you can add the no-stale label |
|
Follow-up on the Vite patch releases: I bumped Vite to Result: latest Vite 8 does not remove the need for the Checks:
Builds run:
Conclusion: keep the CSS layer patch. |
There are currently two vite plugins that are not fully compatible yet:
esbuildoption was specified by "vite-plugin-node-polyfills" plugin. This option is deprecated, please useoxcinstead davidmyersdev/vite-plugin-node-polyfills#142inlineDynamicImportsshould be replaced withcodeSplitting: falsevite-pwa/vite-plugin-pwa#912At first glance, I do not see any issues at runtime though.