For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

you should @import from your code base and set public path. ( e.g. in your case https://example.com/ ). If you need assets public path you can use https://webpack.js.org/configuration/module/#rulegeneratorpublicpath

@vankop My bad, I have surely put a bad description and so you misunderstood the issue.
When enabling CSS experiments, node cannot parse the following CSS codes:

/* test/configCases/css/external/style2.css */
body {
	background: url(//example.com/image.png) url(https://example.com/image.png);
	background-image: url(http://example.com/image.png);
}

/* test/configCases/css/external/style.css */
@import "style2.css";
@import "https://test.cases/path/../../../../configCases/css/external/external.css";

if you want to handle http/https protocol urls ( bundle assets from this protocol requests ) you should just enable https://webpack.js.org/configuration/experiments/#experimentsbuildhttp

But it's not the wanted behavior. I don't want to bundle the remote CSS in the current compilation, I want Webpack to let me use the standard CSS behavior as described in https://developer.mozilla.org/en-US/docs/Web/CSS/@import.
The web target build already handles that thanks to the code I duplicated for the node target: https://github.com/webpack/webpack/blob/main/lib/WebpackOptionsApply.js#L141-L163.

yeah.. as I said in separate PR we should support ignore option.. #15821

Sorry, I disagree. Why don't you want to hack the source assets with magic comments when you can easily handle the code?

ok.. in css instead of ignoring request webpack creates ExternalModule and there is no support for node

ok.. in css instead of ignoring request webpack creates ExternalModule and there is no support for node
Yes

My test is failing in some cases because I try to check that the @import rule is in the bundled file, have you any idea to do another way than mine?

@vankop @sokra Do you think this PR could be merged?

@vankop @sokra Do you think this PR could be merged?

up 🙄

@noreiller @sokra on vacation, he will be here in near future, your PRs on our radar, so don't worry

Oh ok! Thanks for the update.

Thanks