Subset of #121345. 🚧 Draft to get discussions started.

As an addition to the planned "New …" #124304 contribution point, VS Code wants to make it easier to get started with TypeScript by generating a folder with all the necessary files. The script could introduce the key aspects of TS and VS Code's capabilities and provide a playground to try them out.

What could the user flow be?

The ecosystem of CLI tools for project bootstrapping is vivid across most languages. Every major JS/node project provides their own tool. VS Code's built-in Terminal would therefor be the perfect entry point for project creation.

1. (Welcome) "New …" → (Quick prompt) "TypeScript Starter"
2. 💪 Pick container or local folder
3. Native dialog to pick a new or existing folder
4. Attach VS Code window to selected folder
5. Open Terminal with tsc --init command that guides the user through the wizard (frontend, backend, fullstack)
6. The generated TS index file opens and contains a basic TS snippet hello world + next steps (how to run, complex, next steps) in comments

Other variations:

• Open Terminal in current VS Code window and give the user the option to open the window when the command ran
• Detect if node/npm is installed and guide user through the installation if needed

How should the entry point be called?

• "New TypeScript Project"
  • 👍 Often used for similar concepts
  • 👎 Project is a overloaded term in code environments and not used in VS Code
• "New TypeScript Configuration"
  • 👍 TSConfig reference
  • Does not imply that it creates a new folder/workspace, but maybe could be run in an existing folder
• "TypeScript Frontend" | "TypeScript Backend" | "TypeScript Fullstack"
  • 👍 One for each to avoid naming it
  • 👍 Makes the use case clearer for beginners
  • Not many languages are fullstack, so it wouldn't be a common pattern

cc @gcrev93 @JacksonKearl @misolori @DanielRosenwasser