SmartThings CLI v2 on Windows fails #815
Description
Is your feature request related to a problem? Please describe.
As a developer I spend alot of time keeping my development machine functional. I have C/C++/JS and a multitude of packages, scripts and you-name it. 90% of the npm, vcpkg and repo clones work just just fine. THIS smartthings-cli tool? Not great - it wants to launch visual code because, I want .js files to be associated with visual code. no matter what i do i can't seem to get the cmd to function, even with help from Chat. smartthings --version just opens a .js file. SmartThings CLI v2 on Windows and it is completely unusable out-of-the-box.
Issues include:
smartthings --version fails because .js files open in VS Code by default.
Direct Node calls to dist/index.js or dist/src/cli.js fail because the expected entry files do not exist.
Global npm install doesn’t reliably create shims that PowerShell or CMD can run.
There is no documented, working way to use the CLI on a standard Windows machine without hacking PATH or writing functions.
This makes it impossible to develop Edge drivers or run CLI commands without workarounds. A basic, functional development environment should be a requirement for CLI v2.
Please prioritize Windows compatibility and document a reliable setup process — as it stands, the CLI cannot be used by Windows developers.
Describe the solution you'd like
smartthings-cli shouldn't clash with other tools likely to be on a development machine.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.