fix(compiler): resolve entrypoint from exports["."]["typespec"] when tspMain is absent

[Copilot]

tsp compile . only checked tspMain for entrypoint resolution, ignoring the exports field. Libraries using exports["."]["typespec"] without tspMain couldn't be compiled directly from their directory.

Changes

• packages/compiler/src/utils/misc.ts — resolveTspMain now falls back to exports["."]["typespec"] when tspMain is not set. Priority order:

  1. entrypoint in tspconfig.yaml
  2. tspMain in package.json
  3. exports["."]["typespec"] in package.json ← new
  4. main.tsp (default)

• packages/compiler/test/core/entrypoint-resolution.test.ts — added tests covering the new fallback, tspMain precedence, and tspconfig.yaml precedence.

Example

A library with this package.json (no tspMain) now works with tsp compile .:

{
  "exports": {
    ".": {
      "typespec": "./lib/main.tsp",
      "default": "./dist/index.js"
    }
  }
}

• Fixes tsp compile . doesn't resolve entrypoints from exports #6219

[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@11423

commit: 9abe4ee

[github-actions]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - fix ✏️

tsp compile . now resolves the entrypoint from exports["."]["typespec"] in package.json, taking precedence over the legacy tspMain field

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension