I am trying to setup the 'best' environment for using DX for all my development work, specifically the 'best' Command Line tool. I am running Windows 10 and use Illuminated Cloud + Webstorm as my main IDE. I was able to get the regular windows cmd.exe to work just fine as my Terminal, but many, if not all the examples of extending the CLI are using some form of Bash (I think all SFDC engineers use Macs now). For instance, I was hoping to get something like this auto completion to work in my command line tool.
So I decided to give the Windows Subsystem for Linux (WSL) a try since that feels like it would be the best option for getting BASH scripts to work in a Windows environment, and unlike Git Bash and other tools, it is supposed to be supported if I understand the docs correctly.
I was able to get the command tool installed in the WSL running Ubuntu, but I cannot get the
force:auth:web:login to work. After some digging around, it looked the issue might that it needs the PATH set for the browser to work. So I did that, and I am able to execute chrome.exe and sensible-browser as commands and they launch Chrome in an empty window. I was able to get the command to launch a browser window at some point, but the URL just had
in the URL bar. When I installed the CLI in a virtual Linux box, I was able to get it to work, so seems to be something to do with how the WSL interacts with the host windows environment ( at a core level I realize it isn't designed to work with the GUI)
So has anyone made this setup work? Or I am just wasting my time? Is the WSL just designed for CI type interactions that don't require any browser interactions? And if so, what terminal tools are folks using with Windows 10? Pretty much every demo and doc I read is assuming the user is on a Mac, so is there a good way I can setup DX on Windows but still take advantage of the other tools folks are building for the CLI?