Add support for scroll-state container queries

[bakura10]

Hello,

Chrome will soon add support for scroll-state container queries. For now Lightning CSS is not able to compile them. Plese find a reproduction here.

Thanks.

[lcoronelp]

I had to change the build to stop minimizing with this tool since there is no way to make it work.

[nnmrts]

I had to change the build to stop minimizing with this tool since there is no way to make it work.

@lcoronelp, how did you do that? And do you use tailwind perhaps?

[klimashkin]

It was released in Chrome 133, would be great to have the syntax support in LightningCSS

[ggPeti]

Another instance of Parcel not following the robustness principle: be liberal in what you accept, be conservative in what you produce. (See also parcel-bundler/parcel#6111). Strong red flag, avoid parcel, use webpack.

[devongovett]

lol chill. It's just a feature that hasn't been implemented yet. You're welcome to contribute.

[ggPeti]

It's just a feature that hasn't been implemented yet.

Categorically disagree. A robust preprocessor shouldn't just remove code it cannot interpret. In your approach, every new language feature creates "a feature that's not yet implemented" in the preprocessor. The missing feature is the symptom - not adhering to the right design principles is the fundamental problem.

[t0byman]

I opened a PR for this: #1031

[t0byman]

Can we get this merged guys?

[ggPeti]

@devongovett bumping this

[jonnitto]

@devongovett Can we have the pr #1031 merged and released? this would be awesome!

[azu]

This issue is becoming increasingly important as Next.js 16 (stable released October 21, 2025) now uses Turbopack as the default bundler, which relies on lightningcss for CSS parsing.

When a CSS file contains @container scroll-state(...) queries, Turbopack builds fail:

> next build

   ▲ Next.js 16.0.7 (Turbopack)

> Build error occurred
Error: Turbopack build failed with 1 errors:
./path/to/globals.css:5007:13
Parsing CSS source code failed
> 5007 |   @container scroll-state(stuck:inline-end) {

While next build --webpack works as a workaround, this forces users to opt out of the default bundler just to use scroll-state container queries.

[theosiemensrhodes]

@devongovett Bumping this. This is really disappointing that a fix has been ready for 6 months and not been merged.