feat(compiler): Add back empty project template to tsp init

[Copilot]

Restores the "Empty project" option to tsp init — users wanted a minimal scaffold to start from scratch rather than being forced to choose a richer template.

Changes

• templates/scaffolding.json — Added "empty" template (no libraries, no emitters, basic kind: project config)
• templates/__snapshots__/empty/ — Snapshot files for the generated output: empty main.tsp, minimal package.json (compiler-only), standard tspconfig.yaml and .gitignore
• test/e2e/init-templates.e2e.ts — Added snapshot generation and compile validation for the empty template

The empty template produces:

my-project/
├── .gitignore
├── main.tsp          # empty — start here
├── package.json      # @typespec/compiler only
└── tspconfig.yaml    # kind: project + commented options

• Fixes Add back empty project tsp init option #6858

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/compiler@11476

commit: 65ce066

[timotheeguerin]

@copilot did you rebuild?

Run node eng/common/scripts/check-for-changed-files.ts
 M packages/compiler/templates/scaffolding.json

ERROR: Files above were changed during PR validation, but not included in the PR.
Include any automated changes such as sample output, spec.html, and ThirdPartyNotices.txt in your PR.
Error: Process completed with exit code 1.

[Copilot]

@copilot did you rebuild?

Run node eng/common/scripts/check-for-changed-files.ts

...

Fixed in the latest commit. The scaffolding.json is auto-generated by .scripts/build-init-templates.ts — I was editing scaffolding.json directly before. I've now added the empty template to the build script and regenerated scaffolding.json from it.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension