Right now we prompt the user to run npm install, and we do so in a command prompt window that must be dismissed before the project wizard finishes and the project loads in solution explorer.
When you have lots of windows open, it's easy to forget that command prompt window, and then you look at VS which seems to be stuck creating the project, and it's just waiting for you to close the command prompt.
We probably should keep the prompt to run npm install, but we should load the project and invoke npm's 'install missing modules' command, which logs to VS output window, and does not need to be dismissed.
When you have lots of windows open, it's easy to forget that command prompt window, and then you look at VS which seems to be stuck creating the project, and it's just waiting for you to close the command prompt.
We probably should keep the prompt to run npm install, but we should load the project and invoke npm's 'install missing modules' command, which logs to VS output window, and does not need to be dismissed.