microsoft / microsoft/TypeScript

tsc --build / Project References Feedback & Discussion

Open
#25,600 141 comments 44 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Discussion Scenario: Monorepos & Cross-Project References
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

Continuation of #3469 "Medium-sized Projects" which has grown too large for GitHub to display comfortably

Please use this thread for feedback, general discussion, questions, or requests for help / "is this a bug" discussions.

Active bugs / PRs in this area:

Possible next steps:

  • (none yet; @andy-ms) Find unloaded downstream projects during rename
  • #25376 Infer project references from monorepo tooling package.json files
  • #25562 Terse mode output for tsc -b
  • (none yet; @weswigham ?) Intermediate build outputs to temp folders
  • (none; stretch) Parallelization / worker processes under tsc -b

Other interesting links:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the outline in issue #3469 and the linked project-references examples to understand the scope of tsc --build. Choose a concrete follow-up such as #25376 or #25562, then use that issue's acceptance criteria to define what done means; this thread itself has no single implementation target.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.