PR with a failing test to replicate this bug: #438. I've made some progress tracking down why this happens, but still haven't figured out the right way to fix it. Feel free to take a stab at it yourself, BTW, otherwise, I'll keep working on this as I get time.
There is probably no right answer on how to handle charset since you could theoretically find them anywhere in the root file, or imported files, but at the end of the day there needs to be at most one. Looks like all files that get @imported in get brought in as utf-8, but the root passed in css file contents could be any encoding, so it may not be safe to assume that everything could have @charset "UTF-8" slapped at the top.
Previously opened an issue with angular, but I've isolated the issue to this library.
The incoming css looks like
but after passing through this plugin, the @import is listed above the @charset. @charset needs to be listed first to work.
The text was updated successfully, but these errors were encountered: