-
-
Notifications
You must be signed in to change notification settings - Fork 149
Different CSS Module class name in SSR and Client side output #351
Comments
Hi @znck! I did some investigation about that issue. at first it looked like a postCss problem which does not use correct clousure to encapsulate Here is PR to |
Thanks for taking the time to resolve this, much appreciated. PR is merged and a new version has been released. |
Thanks for fast response! I tested fix in that way on my localmachine:
Sorry for creating this bug 😢 |
Released the patch with your fix. |
Version
5.0.0
Reproduction link
https://github.com/przemkow/rollup-plugin-vue-css-modules-issue
Steps to reproduce
git clone https://github.com/przemkow/rollup-plugin-vue-css-modules-issue
run:
What is expected?
both
cjs
andesm
output should contain the same class names after compilation of css modulesWhat is actually happening?
Server side optimised build (
optimizeSSR: true
) and client side build (optimizeSSR: false
) generates different class names for the same CSS module element.This behaviour is present only if we run production build. (
isProduction: true
,NODE_ENV=production
etc.) without production template optimisation both files contains the same output class name.The text was updated successfully, but these errors were encountered: