[Timothee Guerin (timotheeguerin)]

Subpath emitters currently collapse to their parent package's name: their own options are ignored, default output folders collide, and progress/timing reports cannot distinguish them.

Resolve identity from the entry point's $lib.name during library loading, keeping version/support metadata from package.json. An export @org/emitters/ts declaring $lib.name = "@org/emitters/typescript" can now use:

emit:
  - "@org/emitters/ts"
options:
  "@org/emitters/typescript":
    max-files: 10

Its default output directory and runtime reporting use @org/emitters/typescript, independent of the alias or filesystem path used to load it. Package-keyed options remain a compatibility fallback. To retain an existing shared output directory, set emitter-output-dir explicitly.

Fixes #10200.

Alternative to #12447, following the library-loading feedback on the earlier attempt.

[pkg-pr-new]

Open in StackBlitz

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

commit: 344a517

[github-actions]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - fix ✏️

Resolve emitters exported from package subpaths using their declared $lib.name, giving each emitter its own options, default output directory, and runtime reporting. Package-keyed options remain supported as a fallback.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension