Ignored imports cause re-ordering of CSS

[romainmenke]

This has been part of this plugin since the first release :

postcss-import/index.js

Line 77 in 319c4f7

if (parsedAtImport.path.match(/[a-z]+:\/\//i)) {

current code :

postcss-import/lib/parse-styles.js

Lines 29 to 37 in 4dbc931

	// skip protocol base uri (protocol://url) or protocol-relative
	if (stmt.type !== "import" || /^(?:[a-z]+:)?\/\//i.test(stmt.uri)) {
	continue
	}
	if (options.filter && !options.filter(stmt.uri)) {
	// rejected by filter
	continue
	}

---

@import "foo.css";
@import "https://font.service/my-font.css";
@import "bar.css";

It will be re-ordered by postcss-import :

@import "https://font.service/my-font.css";
foo{}
bar{}

---

I think we should at least warn when this scenario happens :

• an @imports can not be inlined
• it follows other @imports's that were inlined

[RyanZim]

Yeah, a warning would be prudent here.

[romainmenke]

I didn't find a good way to add a warning for this edge case without adding a lot of complexity.

I did however recently created a stylelint plugin with some warnings for edge cases in CSS bundlers.

I also added a warning for this edge case there : https://github.com/csstools/postcss-plugins/blob/3163647e778da39116303234e82f0049f7f07560/plugins-stylelint/no-invalid-at-import-rules-when-bundling/index.test.js#L61-L67

I suggest we close this issue as won't fix