New compiled CSS is not seen as new by Styleguidist or Jest.

[GoOz]

While working locally, any new compilation of CSS due to any change does not:

• trigger a hot-reload on Styleguidist, it can see the change, says it's compiling but doesn't reload and even if you manually reload CSS stays the same as before, the new css is not compiled or refreshed.
  Workaround: You have to re-launch Styleguidist manually with CLI.
• Jest keeps the old CSS in cache and never update it, therefore tests fails to be right. Tests fail when they shouldn't and updating tests fail too.
  Workaround: Run a yarn jest --clearCache before running any other jest command.

[y-lohse]

Possible lead : https://webpack.js.org/plugins/mini-css-extract-plugin/#advanced-configuration-example

[y-lohse]

After some more exploration of the problem, it seems that:

• we are displaying transpiled components in the styleguidist (yay)
• but the stylesheet for the transpiled components is not re-generated when a stylus file changes

Still investigating.

[y-lohse]

No luck this time. More notes for next time:

• the stylesheet is generated by babel
• stylus changes are detected… but they don't trigger a new build of transpiled/stylesheet.css

[y-lohse]

Some more infos, it seems related to michalkvasnicak/babel-plugin-css-modules-transform#27 and we have the same issue in cozy-sharings for example. It's a known limitation of the plugin we use and it's unlikely to be fixed.

The problem can be mitigated a little by setting devMode to true in the options. With that option, the stylesheet is rebuilt when js files are changed. It still doesn't rebuild it when the stylus files are changed though.

A longer term solution would probably be to change our stylus compilation setup entirely.

[ptbrowne]

I am closing, it's been a long time since we haven't had any report of the issue, please re-open if necessary.