vscode-cssvar: The extension stopped working again
This extension will soon make me hysterical 😃
Then everything worked, but now I have deployed a larger project and everything has apparently broken…
Did everything exactly the same as then, but it still issues a warning:
Here are my settings in the global file — setting.json
I also attach screenshots from the package.json file and node_modules folder with proof that I have installed the necessary packages:
The funny thing is that everything works well with CSS files, but as soon as I move into a project where variables are written in SCSS files, everything immediately stops working and knocks out a warning, which is shown in the very first screenshot. Running VS Code as an administrator didn’t solve the problem either. Maybe I forgot to do something, but that’s just not clear to me yet. Either, I did everything right, and it’s already about expansion.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 38 (20 by maintainers)
Commits related to this issue
- [#36] fix: set undefined for empty workspace folders value — committed to willofindie/vscode-cssvar by phoenisx 2 years ago
- [#36] fix: set undefined for empty workspace folders value — committed to willofindie/vscode-cssvar by phoenisx 2 years ago
- [#36] fix: platform specific file paths — committed to willofindie/vscode-cssvar by phoenisx 2 years ago
- [#36] fix: platform specific file paths — committed to willofindie/vscode-cssvar by phoenisx 2 years ago
Now there is no error and everything works fine 😌 But! There is another interesting point
The following error is displayed in VS Code DevTools
When I started the extension locally, this error was also displayed in the VS Code console
Maybe this is also somehow related to Windows
I managed to solve the problem!!! 🤩 In general, yes, if you replace
pathwithfsPath, then the error does not appear The trick is that in Windows OS, a backslash is used in the paths —\, most likely this was the cause of the problem I think it’s not for nothing that all this happened because now you will know that on Windows, paths are written a little differently 😇The terminal did not issue an error when executing the command
It turns out that the problem is not on my side? Anyway, I will wait for version 2.0 😇
Is it possible that it’s all about the extension itself? I tried to install a similar extension —
vunguyentuan.vscode-css-variablesand it worked for me. Yes, it also works with jambs, but still. I’m just curious to figure out what the problem is… 😇