Unify typespec-ts coverage and migrate spector upload into this repo (#4750)

## Summary

RLC support for the TypeScript emitter has been dropped, and the emitter
(`@azure-tools/typespec-ts`) now lives in this repo (migrated from the
now-deprecated `Azure/autorest.typescript`). This PR unifies the
dashboard presentation and brings the coverage upload home.

### Website (`can-i-use/http.astro`)
- Collapsed the two TypeScript rows (RLC + Modular) into a single
`@azure-tools/typespec-ts` entry in both the data-plane and
management-plane emitter lists.
- Renamed the displayed language flavor from "TypeScript (Modular)" /
"TypeScript (RLC)" to **"JavaScript"**.

### Coverage upload (`eng/pipelines/jobs/build-for-publish.yml`)
The spector coverage upload for typespec-ts previously ran only in
`Azure/autorest.typescript` (`.scripts/ci.yml`, branch `v6`), uploading
`@azure-tools/typespec-ts-modular` and `@azure-tools/typespec-ts-rlc`.
That job was never migrated when the emitter moved here. This adds a
parallel upload mirroring the existing Python block:
- Runs `pnpm run test:ts:e2e` in `packages/typespec-ts`.
- Uploads the resulting coverage via `tsp-spector upload-coverage` under
the unified generator name `@azure-tools/typespec-ts` (mode `azure`),
using the same storage account / `coverages` container convention as the
other emitters.

### Cleanup
- Dropped `modular` from the generated coverage file name
(`spector-coverage-typescript-azure.json`).

## Notes / follow-ups
- **Data gap:** the dashboard's JavaScript column will be empty until
the next publish build runs on `main` and produces the first
`@azure-tools/typespec-ts` coverage blob.
- **Retire old job:** once this lands, the
`@azure-tools/typespec-ts-modular` / `-rlc` upload in
`Azure/autorest.typescript` `.scripts/ci.yml` can be removed.
- **Standard mode:** only the `azure`-mode upload is wired, since the
dashboard renders `modes: ["azure"]` and the repo's
`integration-test-ci` only runs the azure-modular server. Standard-mode
parity can be added later if desired.

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: xirzec

.chronus/changes/typespec-ts-spector-coverage-rename-2026-6-29-14-42-0.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - "@azure-tools/typespec-ts"
+---
+
+Simplify the test/spector npm scripts now that the TypeScript emitter only produces a single unified (Azure modular) output: drop the redundant `:azure-modular`/`:modular` script-name suffixes and pass-through aliases, remove the dead non-Azure `start-test-server` and the unused `test:azure`/`test:ts:e2e`/`integration-test-ci:sequential` scripts, and rename the spector coverage file to drop `modular` from its name.

.github/instructions/typespec-ts.instructions.md

@@ -35,7 +35,7 @@ The package is tested through vitest projects (see `vitest.config.ts`):
 - `integration-azure-modular` — `test/azure-modular-integration/**` (Modular spector e2e).
 
 Run them with `pnpm test-next`, `pnpm unit-test` (runs the modular unit project),
-and `pnpm integration-test-ci:azure-modular`.
+and `pnpm integration-test-ci`.
 There is intentionally no non-Azure integration project — coverage for those scenarios
 is a superset within the `azure-*` folders.
 
@@ -81,7 +81,7 @@ Integration (spector) tests generate real clients from specs, then assert on the
      subprocess per compile.
    - `--phase=declarations` emits the tracked `src/index.d.ts` baseline (tsc `.d.ts` +
      api-extractor rollup). Only `check:tree` consumes these, so the e2e script
-     `generate-and-run:azure-modular` runs the vitest suite in parallel with the
+     `generate-and-run` runs the vitest suite in parallel with the
      declaration regen, keeping the (slow) api-extractor work off the test critical path.
 3. The vitest `integration-azure-modular` project then runs the `*.test.ts` assertions.
 
@@ -100,7 +100,7 @@ must run before `check:tree`.
 
 ## CI: `e2e-test` job in `.github/workflows/ci-typescript.yml`
 
-The e2e job runs `copy:typespec` → `integration-test-ci:azure-modular` →
+The e2e job runs `copy:typespec` → `spector-test` →
 `pnpm check:tree`. `check:tree`
 (`test/commands/check-clean-tree.ts`) **fails if regeneration leaves the git tree dirty**.
 So a baseline that doesn't match freshly generated output (changed, missing, or added

.github/workflows/ci-typescript.yml

@@ -58,9 +58,9 @@ jobs:
       - name: Copy TypeSpec files
         working-directory: packages/typespec-ts
         run: pnpm copy:typespec
-      - name: Run Modular Spector tests
+      - name: Run Spector tests
         working-directory: packages/typespec-ts
-        run: pnpm integration-test-ci:azure-modular
+        run: pnpm spector-test
       - name: Check git tree is clean
         working-directory: packages/typespec-ts
         run: pnpm check:tree

eng/pipelines/jobs/build-for-publish.yml

@@ -41,6 +41,30 @@ jobs:
           PackagePath: packages/typespec-python
           GeneratorName: "@azure-tools/typespec-python"
 
+      # TypeScript (typespec-ts) e2e tests and spector coverage upload.
+      # The emitter was migrated here from Azure/autorest.typescript; this replaces
+      # the coverage upload that previously ran in that (now deprecated) repo.
+      - script: pnpm run integration-test-ci
+        displayName: "Run TypeScript e2e tests"
+        workingDirectory: packages/typespec-ts
+
+      - task: AzureCLI@2
+        displayName: "Upload spector coverage (typespec-ts, azure)"
+        continueOnError: true
+        inputs:
+          azureSubscription: "TypeSpec Storage"
+          scriptType: "bash"
+          scriptLocation: "inlineScript"
+          inlineScript: >-
+            npx tsp-spector upload-coverage
+            --coverageFile ./coverage/spector-coverage-typescript-azure.json
+            --generatorName "@azure-tools/typespec-ts"
+            --storageAccountName typespec
+            --containerName coverages
+            --generatorVersion $(node -p -e "require('./package.json').version")
+            --generatorMode azure
+          workingDirectory: packages/typespec-ts
+
       - template: /eng/pipelines/templates/pack.yml
         parameters:
           artifactName: npm-packages-stable

packages/typespec-ts/CONTRIBUTING.md

@@ -36,16 +36,16 @@ the required tooling (Node.js and `pnpm`). The command scripts under `test/comma
 
 The package is tested through three vitest projects (configured in `vitest.config.ts`):
 
-| Project                     | Location                            | Covers                           | Command                                  |
-| --------------------------- | ----------------------------------- | -------------------------------- | ---------------------------------------- |
-| `test-next`                 | `test-next/**`                      | Modern unit tests                | `pnpm test-next`                         |
-| `unit-modular`              | `test/modular-unit/**`              | Modular unit tests               | `pnpm unit-test`                         |
-| `integration-azure-modular` | `test/azure-modular-integration/**` | Modular spector end-to-end tests | `pnpm integration-test-ci:azure-modular` |
+| Project                     | Location                            | Covers                           | Command                    |
+| --------------------------- | ----------------------------------- | -------------------------------- | -------------------------- |
+| `test-next`                 | `test-next/**`                      | Modern unit tests                | `pnpm test-next`           |
+| `unit-modular`              | `test/modular-unit/**`              | Modular unit tests               | `pnpm unit-test`           |
+| `integration-azure-modular` | `test/azure-modular-integration/**` | Modular spector end-to-end tests | `pnpm integration-test-ci` |
 
 `pnpm lint` runs ESLint with `--max-warnings=0`.
 
 The integration suite generates real clients from specs and runs them against a local spector
-test server; `pnpm integration-test-ci:azure-modular` starts the server, generates, and runs the
+test server; `pnpm integration-test-ci` starts the server, generates, and runs the
 assertions for you. To (re)generate the tracked baselines without running the tests:
 
 ```bash
@@ -96,7 +96,7 @@ pnpm check:tree        # fails if regeneration left the git tree dirty
 
    ```bash
    pnpm copy:typespec
-   pnpm generate-tsp-only:azure-modular:client
+   pnpm generate-tsp-only:client
    ```
 
    Once your change is complete, regenerate the whole suite and verify there are no unexpected

packages/typespec-ts/package.json

@@ -20,28 +20,21 @@
     "clean": "rimraf ./dist ./typespec-output",
     "build": "tsc -p .",
     "test": "npm run test-next && npm run unit-test && npm run integration-test-ci",
-    "test:azure": "npm run test-next && npm run copy:typespec && npm run integration-test-ci:azure-modular",
     "lint": "eslint . --ext .ts --max-warnings=0",
     "lint:fix": "eslint . --fix --ext .ts",
     "check:tree": "node ./test/commands/check-clean-tree.ts",
-    "test:ts:e2e": "npm run copy:typespec && npm run integration-test-ci:azure-modular",
-    "integration-test-ci": "npm-run-all copy:typespec integration-test-ci:azure-modular",
-    "integration-test-ci:sequential": "npm-run-all --serial copy:typespec integration-test-ci:azure-modular",
-    "integration-test-ci:azure-modular": "npm-run-all --silent -p start-test-server:azure-modular --race generate-and-run:azure-modular",
-    "start-test-server": "mkdirp -p coverage && npx tsp-spector serve ./node_modules/@typespec/http-specs/specs  --coverageFile ./coverage/spector-coverage-typescript.json",
-    "start-test-server:azure-modular": "mkdirp -p coverage && npx tsp-spector serve ./node_modules/@azure-tools/azure-http-specs/specs ./node_modules/@typespec/http-specs/specs --port 3002  --coverageFile ./coverage/spector-coverage-typescript-modular-azure.json",
+    "integration-test-ci": "npm-run-all copy:typespec spector-test",
+    "spector-test": "npm-run-all --silent -p start-test-server --race generate-and-run",
+    "start-test-server": "mkdirp -p coverage && npx tsp-spector serve ./node_modules/@azure-tools/azure-http-specs/specs ./node_modules/@typespec/http-specs/specs --port 3002  --coverageFile ./coverage/spector-coverage-typescript-azure.json",
     "copy:typespec": "node ./test/commands/copy-typespec.ts",
-    "generate-and-run:azure-modular": "npm run generate-tsp-only:azure-modular:client && npm-run-all -p integration-test:alone:azure-modular generate-tsp-only:azure-modular:declarations && npm run stop-test-server -- -p 3002",
-    "generate-tsp-only": "npm run generate-tsp-only:azure-modular",
-    "generate-tsp-only:azure-modular": "node ./test/commands/gen-spector.js",
-    "generate-tsp-only:azure-modular:client": "node ./test/commands/gen-spector.js --phase=client",
-    "generate-tsp-only:azure-modular:declarations": "node ./test/commands/gen-spector.js --phase=declarations",
+    "generate-and-run": "npm run generate-tsp-only:client && npm-run-all -p integration-test:alone generate-tsp-only:declarations && npm run stop-test-server -- -p 3002",
+    "generate-tsp-only": "node ./test/commands/gen-spector.js",
+    "generate-tsp-only:client": "node ./test/commands/gen-spector.js --phase=client",
+    "generate-tsp-only:declarations": "node ./test/commands/gen-spector.js --phase=declarations",
     "regen-test-baselines": "npm run generate-tsp-only",
-    "integration-test:alone": "npm run integration-test:alone:azure-modular",
-    "integration-test:alone:azure-modular": "vitest run --project integration-azure-modular",
+    "integration-test:alone": "vitest run --project integration-azure-modular",
     "stop-test-server": "npx tsp-spector server stop",
-    "unit-test": "npm run unit-test:modular",
-    "unit-test:modular": "cross-env NODE_OPTIONS=--max-old-space-size=1024 vitest run --project unit-modular",
+    "unit-test": "cross-env NODE_OPTIONS=--max-old-space-size=1024 vitest run --project unit-modular",
     "gen:scenario-suites": "node ./test/commands/gen-scenario-suites.ts",
     "regen-docs": "npm run build && tspd doc . --enable-experimental --output-dir ../../website/src/content/docs/docs/emitters/clients/typespec-ts/reference --skip-js"
   },

website/src/pages/can-i-use/http.astro

@@ -16,8 +16,7 @@ const options: CoverageFromAzureStorageOptions = {
     "@azure-tools/typespec-python",
     "@azure-tools/typespec-go",
     "@azure-typespec/http-client-csharp",
-    "@azure-tools/typespec-ts-rlc",
-    "@azure-tools/typespec-ts-modular",
+    "@azure-tools/typespec-ts",
     "@azure-tools/typespec-java",
     "@azure-tools/typespec-cpp",
     "@azure-tools/typespec-rust",
@@ -28,8 +27,7 @@ const options: CoverageFromAzureStorageOptions = {
     "@azure-tools/typespec-python": "Python",
     "@azure-tools/typespec-go": "Go",
     "@azure-typespec/http-client-csharp": "C#",
-    "@azure-tools/typespec-ts-rlc": "TypeScript (RLC)",
-    "@azure-tools/typespec-ts-modular": "TypeScript (Modular)",
+    "@azure-tools/typespec-ts": "JavaScript",
     "@azure-tools/typespec-java": "Java",
     "@azure-tools/typespec-cpp": "C++",
     "@azure-tools/typespec-rust": "Rust",
@@ -47,8 +45,7 @@ const options: CoverageFromAzureStorageOptions = {
         "@azure-tools/typespec-python",
         "@azure-tools/typespec-go",
         "@azure-typespec/http-client-csharp-mgmt",
-        "@azure-tools/typespec-ts-rlc",
-        "@azure-tools/typespec-ts-modular",
+        "@azure-tools/typespec-ts",
         "@azure-tools/typespec-java",
         "@azure-tools/typespec-cpp",
         "@azure-tools/typespec-rust",