Marijn Kok

The issue has been resolved after I reinstalled the plugin. Should have thought of that before. You may concider this fixed!

Using `vitest`, CSS seems to work just fine. Unfortunately I'm also running into issues with psuedo selectors: ``` DOMException: Invalid selector: "::-webkit-inner-spin-button,::-webkit-outer-spin-button" ❯ Function.getSelectorGroups ../../../node_modules/happy-dom/src/query-selector/SelectorParser.ts:186:10 ❯ Function.match ../../../node_modules/happy-dom/src/query-selector/QuerySelector.ts:119:38 ❯ CSSStyleDeclarationElementStyle.parseCSSRules...

I'm testing a nuxt 3 application with `vitest`, with `nuxt-vitest` as test environment. When including the `@nuxtjs/tailwindcss` Nuxt module, I get the above error when running `expect().toBeVisible()`. I've narrowed down...

Just to chime in and provide some feedback - we rely on `pending` a lot, and having to rewrite everything to a separate computed ref or `status === 'idle' ||...

Experiencing the same issue. running `npm i --force` does solve it but it is not a workable solution.

In the meantime, FA 5.1 is out. It would be greatly appreciated if this version is added too :)

> * A new `app-test` template in [nuxt/starter](https://github.com/nuxt/starter) that can initialize `/test` directory. Using `nuxi init -t test --install` can achieve (almost) the same result I am not super familiar...

> I will keep you/this issue posted on any progress but i think adding a starter template for app testing even if limited might be a good start wdyt? thanks...

https://github.com/nuxt/test-utils/issues/775 just mentioning this one here, thanks for taking this up!

Running into this issue as well, a fix or workaround for usage with `msw` would be greatly appreciated.