UX: Visual Studio Publish feature should not require manual Node installation

[lostmsu]

Are you accessing the CLI from the default port :4280 ?

• [ ] No, I am using a different port number (--port) and accessing the CLI from that port
• [ ] Yes, I am accessing the CLI from port :4280
• [x] N/A

Make sure you are accessing the URL printed in the console when running swa start!

N/A

ℹ️ NOTE: Make sure to enable debug logs when running any swa commands using --verbose=silly

N/A

Describe the bug When I use Publish feature in Visual Studio it is a very poor user experience that I have to manually install NodeJS and in it manually install SWA CLI. Visual Studio already comes with NodeJS distribution with few packages installed. It is totally unclear why the feature requires a separate NodeJS/NPM installation. I am not a NodeJS developer. Neither Node, nor NPM are my tools and I only hear about them in forums/social networks.

To Reproduce Steps to reproduce the behavior:

Prereq: there's no system-wide NodeJS installation, and neither node.exe nor npm are in PATH.

1. In Visual Studio publish a web site, and choose a Static Web App resource as a target
2. Hit Publish

Expected behavior

My .html page with a few .js files should publish

[lostmsu]

P.S. command line experience is also very poor. Why not just provide an FTP(S) endpoint like regular Azure Web Service does.