Zack Jackson

So the version in your repo you made was an older one. Either way im not able to replicate this Are you sure youre using the latest copy? These projects...

this syncs it with mini-css and my performance improvement made (currently open pr) https://github.com/faceyspacey/extract-css-chunks-webpack-plugin/pull/226/files

perhaps rm -rf node_moduels, yarn cache clean, yarn --force

Is anyone willing to open a PR if they have found the exact issue? @Timer is there anything I need to do on my side to patch this?

Booooo! Haha all good. I’m maintaining mini-css more than this. Since I merged my hmr capabilities in, I only use this repo to test prereleases of mini css

No I do not. Likely you'd need some prerendering stage to determine what's actually used ahead of time

What about modules. IsonlyLocals still valid?

please add reference to main readme so others can get an idea of what it does

Yes you can “point” to remotes deployed to higher environments or production. We do this all the time You could also shim the remote to return an empty function for...

Set your dev mode app to have react shared as eager:true to force webpack to use your local copy