-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple components: Could not parse CSS stylesheet #4512
Comments
The same problem |
Same problem here. |
@LanFeusT23 @nikitakoliadin @karlfock could you please check this link; https://stackoverflow.com/a/69958999 I saw interesting suggestions when I read the comments in the links he/she shared. :) |
And please see jsdom/jsdom#2177. I think this issue is related to jsdom. So, closed. I use;
Best Regards, |
@mertsincan Thank you! I used this method: jsdom/jsdom#2177 (comment) |
Thanks, it helped. |
Describe the bug
I just upgraded to latest primevue 3.35.0. Before that I had 3.34.1.
When running unit tests with vitest 0.34.5 there are error output from tests that test files that import primevue components. The tests still pass, so there is just a logging that occurs.
In this particular example, it's a component containing a Tag component that is under test.
This is how the logging looks in it's entirety:
Reproducer
https://codesandbox.io/p/sandbox/wonderful-mayer-977h8s?file=%2Fpackage.json%3A18%2C22
PrimeVue version
3.35.0
Vue version
3.x
Language
TypeScript
Build / Runtime
Vue CLI App
Browser(s)
Running test with vitest
Steps to reproduce the behavior
Go to https://codesandbox.io/p/sandbox/wonderful-mayer-977h8s?file=%2Fpackage.json%3A18%2C22
Run in the terminal:
npm test
If you comment out the primevue
Tag
inComponent.vue
and run the test again, there is no "Error: Could not parse CSS stylesheet" etc.See the output:
Expected behavior
Just the test restul without the "Could not parse CSS stylesheet" etc.
The text was updated successfully, but these errors were encountered: