Open katiequakie opened 8 months ago
Update: As a workaround, I deactivated the plugin in my local enviroment, which fixed the issue as stated above. But it would be nice if there was another solution since I find it cumbersome to always be cautious about not checking in the changes and shelving them as soon as I have to change somehing in the plugin configuration.
I'm currently using the media query plugin in a project with scss and a webpack confguration. I was always able to detect the source of css in the devtools via sourcemaps like this:
After installing and configuring the media query plugin, clearing the system cache and restarting filewachters, it successfully splits the output css into seperate chunks, but it doesn't ship their sourcemaps:
Here is what my
webpack.config.js
looks like:How can I get my sourcemaps back? Does it maybe have to do something with the loaders being ignored as stated in Issue #18 (See https://github.com/SassNinja/media-query-plugin/issues/18#issuecomment-519417961)?