Scaffold localization in an extension

[TylerLeonhardt]

I wonder if we can update https://github.com/microsoft/vscode-generator-code to scaffold the l10n directory, add the required "l10n" key to the package.json (once the proposed API is finalized of course), and even include a sample script like the cli.ts. Then we could also have a step in the extension generator which asks you "Do you want to set up localization for this extension" or similar.

Yeah I like this a lot. I'm thinking such a script could:

• create an l10n folder
• update the l10n in package.json
• add @vscode/l10n-dev as a dev dependency
• create a package.nls.json with {} and a big useful comment

I think that @vscode/l10n's scenario is so uncommon that it's probably not worth including that in the generator IMO. Like it's only gonna be useful if your extension has like... a language server or debug adapter written in node (in other words... subprocesses that will only be used by VS Code that aren't in the extension host)

Originally posted by @TylerLeonhardt in microsoft/vscode#162023 (comment)