I use WSL occasionally myself. I did have trouble with using VS Code though, since the VS Code installation was in the Windows part of the machine and so hot reloading wouldn't recognise that I had modified the file until I did a touch from the Linux terminal on the file I had changed. Looks like there's an extension for that now which should fix things.
Unfortunately WSL2 also requires Hyper-V from what I read, and I can't even begin to imagine what issues that will have in addition to the known compatibility issues with other hypervisors and, at least I'd expect, some performance issues.
I use WSL occasionally myself. I did have trouble with using VS Code though, since the VS Code installation was in the Windows part of the machine and so hot reloading wouldn't recognise that I had modified the file until I did a
touchfrom the Linux terminal on the file I had changed. Looks like there's an extension for that now which should fix things.Yea, one of the issues with WSL is that they've failed with the filesystem implementation and it doesn't really work well on either side of it.
I've had more luck with e.g. VirtualBox shared folders mounted on Vagrant VMs and other syncing solutions when I need that to work.
It's worth noting that WSL2 fixes this problem. A Linux kernel ships alongside the Windows kernel in the next update for W10.
Unfortunately WSL2 also requires Hyper-V from what I read, and I can't even begin to imagine what issues that will have in addition to the known compatibility issues with other hypervisors and, at least I'd expect, some performance issues.
To be fair, developing on Windows is like cooking on an electric range. Technically you can do it, but it's far from ideal.