How about ignoring these style files in the unit test plugin?
I think they are not actually tested anyway. Maybe that's less error-prone.

How about ignoring these style files in the unit test plugin?
I think they are not actually tested anyway. Maybe that's less error-prone.

I might be mixing up things, but how would you test css-based things like wrapper.isVisible() with vue-test-utils if visibility, display or opacity comes from an @import/@use or from an @extends that needs this import ?

I might be mixing up things, but how would you test css-based things like wrapper.isVisible() with vue-test-utils if visibility, display or opacity comes from an @import/@use or from an @extends that needs this import ?

Oops. I forgot about that feature.
But I'm wondering if it should be supported at all.

Because the tests are run in Node.js environment with JSDOM, the .isVisible method does not support visibility changes triggered by class styles. It is a known limitation of JSDOM: vuejs/vue-test-utils#1456 So the use case is very limited.

And, the default Jest presets provided by Vue CLI never support such usage (.css files are stubbed in the Jest presets).

Oops. I forgot about that feature.
But I'm wondering if it should be supported at all.

Because the tests are run in Node.js environment with JSDOM, the .isVisible method does not support visibility changes triggered by class styles. It is a known limitation of JSDOM: vuejs/vue-test-utils#1456 So the use case is very limited.

And, the default Jest presets provided by Vue CLI never support such usage (.css files are stubbed in the Jest presets).

Oh didn't know that. Then yeah, you're right, the whole style block of an SFC should simply be ignored.
I don't even know why it wasn't the case from the very beginning since it cannot be interpreted in any way by JSDOM ?

I just update my VUE APP to use Dart-Sass and I get this error on all my test because I use a submodule with all my style-sheets there. Any news aproving this PR or @sodatea the ignore all styles aproche got implemented some where?.

How about ignoring these style files in the unit test plugin? I think they are not actually tested anyway. Maybe that's less error-prone.

Maybe style files can not simply be ignored, since style modules related codes will throw error without these style files.
vue-jest can handle this case.

case:

<template>
  <div :class="$style.hello">
  </div>
</template>

<style lang="scss" module>
.hello {
  display: none;
}
</style>

Hey.

Thanks for everyones great work on this! I have now also run into this problem. What's the horizon for merging this?