[Bug]: CSS output extra details about lang(*) dir(*)

[1yasa]

System Info

System:
OS: macOS 14.4
CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900KF
Memory: 6.79 GB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.8.0 - /usr/local/bin/node
npm: 10.8.2 - /usr/local/bin/npm
pnpm: 9.9.0 - /usr/local/bin/pnpm
bun: 1.1.24 - /usr/local/bin/bun
Watchman: 2024.06.10.00 - /usr/local/bin/watchman

Details

After update to rsapck version > 0.1.4 , build app then output css that has extra unnessary content:

Here is the origin css:

.__editor_block_special {
	padding-inline-start: 0;
	padding-inline-end: 0;
	margin-inline-start: var(--editor_padding_x);
	margin-inline-end: var(--editor_padding_x);
}

Tried custom LightningCssMinimizerRspackPlugin options:

optimization: {
	minimizer: [
		new LightningCssMinimizerRspackPlugin({
			minimizerOptions: {
				exclude: {
					langSelectorList: true,
					dirSelector: true
				}
			}
		})
	]
}

Still dir selector exsit:

Temp resolution is downgrading rspack version to 1.0.4 or set targets to chrome >= 120:

optimization: {
	minimizer: [
		new LightningCssMinimizerRspackPlugin({
			minimizerOptions: {
				targets: 'chrome >= 120'
			}
		})
	]
}

Reproduce link

No response

Reproduce Steps

see above.

[inottn]

Refer to #7811.

[1yasa]

Refer to #7811.

Seem not to solve the problem for default downgrade application css. This default behavior is unacceptable.

[chenjiahan]

Hi, you should set a proper targets for lightningcss, as lightningcss will downgrade modern CSS features to fit to the current target browsers.

[1yasa]

Hi, you should set a proper targets for lightningcss, as lightningcss will downgrade modern CSS features to fit to the current target browsers.

This behavior is unreasonable and unacceptable.

[chenjiahan]

If lightningcss does not downgrade the CSS, it will not work in legacy browsers.

If you have any suggestions on the transformation results of lightingcss, please file an issue in the lightningcss repository: https://github.com/parcel-bundler/lightningcss

[1yasa]

If lightningcss does not downgrade the CSS, it will not work in legacy browsers.

If you have any suggestions on the transformation results of lightingcss, please file an issue in the lightningcss repository: https://github.com/parcel-bundler/lightningcss

My concern stems from rspack's "default settings" here, which are unrelated to lightningcss. Rspak should establish a default configuration that prevents lightningcss from arbitrarily downgrading CSS on its own.

This aligns with developers' understanding of packaging tools like webpack, without the need to delve into any messy details beyond packaging.

[chenjiahan]

I totally understand your claim. Unfortunately, lightningcss does not currently allow to do this. refer to parcel-bundler/lightningcss#792