Please clarify wether HMR should work in the new version

I just want to figure out wether HMR should work with the newest version. I am using the newest version of both this plugin and webpack. It seems that CSS changes are correctly triggering HMR, but in the end nothing happens. This is the client-side log output:

｢hot｣ App updated. Recompiling src/components/card/Card.module.css
log.js:48 ｢hot｣ webpack: Compiling (<unnamed compiler>)
log.js:48 ｢hot｣ App Updated, Reloading Modules
log.js:48 ｢hot｣ Checking for updates to the bundle.
log.js:48 ｢hot｣ No Modules Updated.
log.js:48 ｢hot｣ App is up to date.

Re-loading the app manually works fine though.

This is my loader config for CSS files:

{
  test: /\.module\.(css|sss|pcss)$/,
  use: [
    extractCssLoader,
    "cache-loader",
    "thread-loader",
    {
      loader: "css-loader",
      options: {
        import: false,
        minimize: false,
        sourceMap: true
      }
    },
    {
      loader: "postcss-loader",
      options:{
        sourceMap: true
      }
    }
  ]
}

Any hints? Previously with mini-css-extract-plugin I used the style-loader during development. Is this also the way to go with this plugin?

[ScriptedAlchemy]

@swernerx

Let me know fi this helps, im at work otherwise id dedicate full time to fix it. if you still have issues.

What I had was a conditional checking the the process.env.NODE_ENV === development

secondly I have a function that determines is you use HMR

However id either are false. it won’t add. For the time being you can just add hot:true to the plugin Ill leave that there but will also look at your specific plugin at check if I can automate the test as well

Might appreciate the patience

[ScriptedAlchemy]

No I fully understand! Give me a second and ill release a @next on npm which should resolve your issue