[Christopher Plieger (cplieger)]

When the files parser reaches a file again at a lower depth, it lowers lowestDepth and sets startSubtasks, but the startedSubTasks guard skips the restart because the first arrival already started the file's imports. Those imports keep the first arrival's depth, so a file reached through node_modules first and then from a root file without passing through node_modules leaves its own imports in sourceFilesFoundSearchingNodeModules, and which arrival comes first depends on scheduling.

Impact: in a monorepo where a package is reached both by a relative import and through a node_modules link, which files count as library files changes between identical runs. The same build can then emit different files (#64498), and an analyzer on the API gives a different answer each run: on vitest, 20 opens of one configuration gave five different counts.

The change restarts the subtasks whenever the depth drops, even when they were already started. Each restart strictly lowers a file's lowestDepth, so the extra work is bounded.

The compiler test symlinkedPackageReachedRelativelyIsNotExternalLibrary has a.ts import ./lib/index and b.ts import lib through a node_modules symlink to lib/. Without the change, lib/util.ts counts as from an external library and its util.js is missing from the emit baseline.

I met this while building deadset-ts, the TypeScript analyzer of deadset, on the TypeScript 7 API. That work hit a small set of related defects, which is why a few reports come from me.

An AI coding agent wrote this patch. I have read, built and tested it and will handle the review.

• There is an associated issue in the Backlog milestone (required)
• Code is up-to-date with the main branch
• You've successfully run npx hereby test
• You've successfully run npx hereby lint
• You've successfully run npx hereby check:format
• There are new or updated tests validating the change

Fixes #64498

[Copilot]

Copilot review overview

🟢 Approval recommended

The bounded restart logic addresses the root cause and is covered by a focused regression test.

Review effort: Balanced
Findings: None

What changed in this PR

Fixes nondeterministic external-library classification by propagating reduced node_modules depth through already-started imports.

Changes:

• Restarts file subtasks whenever their discovered depth decreases.
• Adds regression coverage for both root-file orderings.

File	Description
tsc/​internal/​compiler/​filesparser.go	Propagates lowered depth through imports.
tsc/​internal/​compiler/​filesparser_test.go	Verifies deterministic classification.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

Review effort: Lite
Findings: None

[Copilot]

Copilot review overview

🟢 Approval recommended

The bounded restart logic directly addresses the scheduling-dependent classification and is covered by a focused compiler test.

Review effort: Balanced
Findings: None

[Eliseu Videira (eliseuvideira1)]

Could this be picked into release-7.0? 7.0.2 is still latest on npm, and release-7.0 still has the old !taskByFileName.startedSubTasks && loadSubTasks guard.

Through plain tsc, the bug drops a JSON file from outDir on some compiles. A declaration file imports a JSON file, and that declaration file is reached both through a package in node_modules and from a project file. When the node_modules path arrives first, the JSON file counts as a library file and is not written. --explainFiles still lists it in the program.

Repro with one script and five files: https://github.com/eliseuvideira1/ts7-json-emit-repro. Each compiler is a CI job that fails when any compile skips the JSON file. Compiles out of 30 that wrote it, from https://github.com/eliseuvideira1/ts7-json-emit-repro/actions/runs/42379949272 (GitHub-hosted ubuntu-latest, 4 cores):

Compiler	package imported first	local file imported first
7.0.2	28/30	2/30
7.0.2 --singleThreaded	30/30	0/30
7.1.0-dev.20261005.1, 3 commits before this PR	27/30	1/30
7.1.0-dev.20261005.1 --singleThreaded	30/30	0/30
7.1.0-dev.20261006.1, 1 commit after this PR	30/30	30/30
7.1.0-dev.20261006.1 --singleThreaded	30/30	30/30
6.0.3	30/30	30/30

With --singleThreaded and the local file imported first, the skip happens on every compile, because the single-threaded queue loads the last import first. Of the 4 commits between the two nightlies, only this PR changes the file loader.

[Jake Bailey (jakebailey)]

TypeScript Bot (@typescript-bot) cherry-pick this to release-7.0

[typescript-automation]

Starting jobs; this comment will be updated as builds start and complete.

Command	Status	Results
cherry-pick this to release-7.0	✅ Started	✅ Results

[typescript-automation]

Hey, Jake Bailey (@jakebailey)! I've created #65388 for you.