Closed danielkoller closed 8 months ago
Viijay-Kr
commented
9 months ago @danielkoller Thanks for reporting this issue. I apologise for the frustration. This issue could have been a regression since #97 went live. Until I find time to fix this one you could toggle the diagnostics setting off to help you from these annoying red markers
danielkoller
commented
9 months ago @Viijay-Kr thank you for your reply and the great plugin. I will toggle the diagnostics off for now.
Viijay-Kr
commented
8 months ago @danielkoller by any chance do you use jsconfig path aliases ? if so can you share it with me ?
danielkoller
commented
8 months ago Hi @Viijay-Kr, I do. Here you go ->
"paths": { "@/components/": [ "src/components/" ] }
Viijay-Kr
commented
8 months ago Ok that's great .Thanks :). #113 this should fix the issue
Viijay-Kr
commented
8 months ago @danielkoller This should be fixed with the latest version of the extension. Do let me know if you find any issues
danielkoller
commented
8 months ago @Viijay-Kr no issues, thanks for the great work and fast fix. :)
Describe the bug Every styles import throws an error. It says that the module is not found although it is there and the styling is applied. The settings of your extension are default.
To Reproduce Steps to reproduce the behavior: As soon as a file is opened, the import shows an error. Running yarn, restarting the server or reloading the developer window doesn't help.
Expected behavior There should not be an error, because the file is there.
Screenshots
Desktop (please complete the following information):
Additional context Running the latest version of React CSS Modules and played around with older versions - didn't help unfortunately. Thanks for the great extension nonetheless!