Looks like this is implemented by cssom and there is open issue there: NV/CSSOM#109 and not being tackled rrweb-ccsom used currently by jsdom.

I don't think this is implemented by cssom? We switched to rrweb-cssom because cssom was not maintained.

And sorry for wrong title (fixed now), it just reports error on virtual console and classic workaround of providing custom virtual console (possibly silent) helps with at least ignoring this error:

new jsdom.JSDOM('',
  { virtualConsole: new jsdom.VirtualConsole() }
)

There is the same error log when using @layer...

const { JSDOM } = require('jsdom');

new JSDOM(`
  <style>
    @layer {
      .card h2 {
        font-size: 2em;
      }
    }
  </style>
`);

Getting the same @layer error too when attempting to test with PrimeVue components.

Hi everyone,

We are also facing the same problem when having @layer specified in our Css files.
We looked up the source code of CSSOM and the problem is inside the parser() method. The code does not handle correctly some attibutes starting with an @.
We also noticed that this library is no longer maintained by the author . You can see here the repository : CSSOM Repository .

The last version (0.5.0) is now two yeard old and maybe it's time to move on.
Finding an alternative and remove CSSOM from JSDOM dependencies will be great if not too costy for the team.

any known workaround for jest jsdom? I'm facing the issue with primeng and @layer.

Same for me. Unable to test primeng properly.

Any update or workaround about that? I've been stuck in a old primevue version because of that

I made a fork where I added support for @container : https://github.com/mirakl/cssom

in the meantime @domenic and @seanparmelee switched from cssom 0.5.0 to rrweb-cssom 0.6.0 in #3497
rrweb-cssom is maintained by @YunFeng0817 npm/fitz5264

so I moved the @container fix by @romain-blatrix there: rrweb-io/CSSOM#2

lets hope for the best

It has already been merged. Now to hope for a new version being released someday.

Hi jsdom team, v0.7.0 has been published!

thanks @YunFeng0817

I created a pr to bump the version:

#3707

finally the pipeline is green 🎉