Ryan Zimmerman

Merged; this is technically semver-major, so I'm going to try to bundle this with a Node version requirement bump to release.

Released in v15

In regards to the personal access token stuff, I'm not comfortable putting a PAT for my account into the secrets here, especially when I haven't fully vetted the toolchain used...

Yeah, looking at this, it seems case doesn't matter in charset declarations, so we can probably merge them if that's the only difference. PR welcome.

OK, just re-reading this issue, want to make sure I'm not misunderstanding it. The example CSS you posted, is that your actual input CSS to postcss-import?

I'm still not sure I understand. In the latest example you posted, where are the other charset statements?

A reduced test case would be useful here; there shouldn't be a warning if there's only one charset, at the top

Given that a reduced test case has not been presented, and there have been no other reports of this issue, assuming it's some odd configuration issue, closing.

Yeah, if this doesn't require a huge amount of changes (or really hurt performance), PR welcome. I'm personally not motivated to fix this since I always run the output through...

Since https://github.com/postcss/postcss-import/pull/483; this also applies to `@layer` support.