You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using the hard-source-weback-plugin https://github.com/mzgoddard/hard-source-webpack-plugin upon 2nd build no CSS file is emitted for files processed with mini-css-extract-plugin. I have an issue on hard-source but it is not being addressed mzgoddard/hard-source-webpack-plugin#301 and I'm wondering if there is something internally that could be done to mini-css that could fix this issue? I saw past discussions for extract-text-webpack-plugin where caching issues were addressed internally to it that helped it's compatibility with hard-source.
Problem
If using the hard-source-weback-plugin https://github.com/mzgoddard/hard-source-webpack-plugin upon 2nd build no CSS file is emitted for files processed with mini-css-extract-plugin. I have an issue on hard-source but it is not being addressed mzgoddard/hard-source-webpack-plugin#301 and I'm wondering if there is something internally that could be done to mini-css that could fix this issue? I saw past discussions for extract-text-webpack-plugin where caching issues were addressed internally to it that helped it's compatibility with hard-source.
Test Case
Created minimum use case example here https://github.com/dtothefp/hard-cache-mini-css-webpack-4
The text was updated successfully, but these errors were encountered: