Description
I have a gatsby project in my WSL 2 home in the linux file system, i.e. in /home/f00f/my-project/.
For editing in VS Code I go to \\wsl$\Ubuntu-20.04\home\f00f\my-project\ in Windows Explorer and then select "Open in VS Code" in the context menu.
So code lives in linux fs, VS Code runs in Windows, linux fs is shared via network (which is a default WSL 2 feature, not configured by me).
When I enable the extension I get the following error message:
[Error - 16:59:26] Tailwind CSS: ENOENT: no such file or directory, open '\wsl$\Ubuntu-20.04\home\f00f\my-project\tailwind.config.js'
which is almost the correct path. Discovery finds the config file, but normalize-path in server.ts : init() changes the actual path and removes the first backslash. That changes the path from a network path to an absolute path on the current drive on Windows.
Note: in a previous comment I wrote the path in the error message with forward slashes. I cannot reproduce whether it really had forward slashes at that time. Right now I see backslashes.