Backtestsvuerun-20261002-115633#15478

Issue #15478 Merged fix PR #15480 Run 2 Oct 2026 · run-20261002-115633 vuejs/core

compiler-sfc: loadTSConfig re-parses the whole tsconfig extends chain for every config it walks

Worse

The merged fix was judged better than our patch.

In this judgment, Patch B = our agent, Patch A = the merged fix.

Both patches fix the root cause the same way. Each adds a module-level `Map<string, TS.ExtendedConfigCacheEntry>` and passes it as the 8th argument of `parseJsonConfigFileContent`. Each adds a test that counts reads of the shared base config and expects exactly one. That test fails without the cache and passes with it, because the base is read once per extending config otherwise. The difference is invalidation, which the issue names as the caveat a fix must answer.

Patch A clears both `extendedConfigCache` and `tsConfigCache` when a `.json` file is invalidated. Editing `tsconfig.base.json` and invalidating only that file therefore gives fresh results: the parsed parents and the top-level configs that extend the base are both dropped. Non-config edits (.vue/.ts) leave the extended cache intact, so the benefit survives dev/HMR churn.

Patch B clears the extended cache on every `invalidateTypeCache` call, including each SFC or TS edit. This needlessly discards the cache in dev. It also does not drop `tsConfigCache` entries for configs that extend the edited base. B's own staleness test has to call `invalidateTypeCache('/tsconfig.json')` as well, and admits that the extends relationship is not tracked. So in B, invalidating the edited base alone still leaves stale resolved configs. A's approach removes that limitation.

B's extra invalidation test adds some coverage, but it would also pass without the patch, so it does not prove the fix. Its comments are thorough. On correctness under the dev/HMR scenario the issue raises, A is the better fix.

The judge saw only the two patches, labelled A and B in random order, with issue links and version numbers removed. The reasoning above is shown verbatim.

Solve

10m 51s

Wall-clock time in the container

Full test suite

No new failures

3,740 passed · 6 skipped · 3,746 total

Contamination audit

Clean

No sign the agent saw the real fix

Patch size

118vs 74 merged

Changed lines, ours vs merged

Vue version

3.5.42 (latest release; also present on main at 5409708)

Link to minimal reproduction

https://github.com/cainrus/vue-compiler-sfc-tsconfig-repro

Steps to reproduce

git clone https://github.com/cainrus/vue-compiler-sfc-tsconfig-repro
cd vue-compiler-sfc-tsconfig-repro
npm install
npm run repro

The generator builds a workspace of 150 packages, each with its own tsconfig.json that
extends one shared base and declares references to its group, plus one SFC per package whose
props type is imported from another package by alias. Both arms compile the same components; the
cached arm differs only in that it supplies an extendedConfigCache, through the public
registerTS hook, as the 8th argument the package leaves undefined.

What is expected?

Parsing the same extends chain repeatedly should reuse the parsed parent configs, as TypeScript's
own extendedConfigCache parameter exists to allow.

What is actually happening?

loadTSConfig calls ts.parseJsonConfigFileContent with five arguments, so the 8th
(extendedConfigCache) is always undefined:

https://github.com/vuejs/core/blob/main/packages/compiler-sfc/src/script/resolveType.ts

const config = ts.parseJsonConfigFileContent(
  ts.readConfigFile(configPath, fs.readFile).config,
  parseConfigHost,           // 2
  dirname(configPath),       // 3
  undefined,                 // 4
  configPath,                // 5
)                            // 6, 7, 8 omitted -- the 8th is extendedConfigCache

and then recurses through project references:

res.unshift(...loadTSConfig(refPath, ts, fs, visited))

So in a workspace whose packages all extend a shared base, that base is re-read and re-parsed once
per config the traversal reaches, and each parse allocates its own fully expanded paths map.
visited is a default parameter: it de-duplicates within one top-level call, never across calls.

Measured on the reproduction — node 22.23.2, @vue/compiler-sfc 3.5.41, typescript 5.9, one arm
per process (tsConfigCache is module scope):

armconfig parsesdistinct expanded paths objectstimeretained heap
stock2900290011.1 s1346.8 MB
cached2900**1**1.9 s30.2 MB

The parse count is identical in both arms. The cache does not remove parses — it makes each one
cheap and stops the expanded options object from being rebuilt. Retained heap is heapUsed after a
forced GC.

On a production Vue monorepo (2432 components, 514 tsconfigs, 4051 project references, a 118 KB
shared base with 1342 paths entries), compiling 400 of its real components through
compileScript with the same two arms:

armconfig parsesdistinct expanded paths objectstimeretained heap
stock7351735025.4 s2615.8 MB
cached7351**3**8.0 s188.7 MB

That is what led to this report: tsconfig parsing dominated the allocation profile of that
application's production build.

Does the cache change the result?

node parity.mjs in the reproduction re-implements loadTSConfig verbatim and runs it twice per
entry config, differing only in the 8th argument, comparing resolved compilerOptions,
projectReferences and fileNames for every parse the traversal produces:

runparses comparedpaths entries comparedmismatches
node parity.mjs400176 000**0**
MUTATE=1 node parity.mjs (cached arm reads a different config)400176 000336
MUTATE=2 node parity.mjs (one paths entry altered after parsing)400176 000400

The two controls are there because a comparator that always prints zero proves nothing. The same
comparison over the production monorepo's configs: 831 parses, 1 116 033 paths entries, 0
mismatches, with the controls reporting 114 and 831.

One consequence worth stating explicitly: with the cache, the expanded options object is **shared
by reference** (that is where the memory saving comes from), so it must not be handed to a consumer
that mutates it. resolveWithTS only reads matchedConfig.config.options, so that holds today.

Suggested fix

A module-level Map threaded into the 8th argument. One caveat a fix has to answer:
invalidateTypeCache currently clears tsConfigCache and tsConfigRefMap, and would need to clear
the new cache too, or an edited tsconfig.base.json would go stale in dev/HMR — TypeScript keys
extendedConfigCache by resolved path, so that is a targeted delete.

PR: #15480 — it also explains why a plain Map rather than createCache(), and why
invalidateTypeCache clears the cache instead of deleting one entry.

System Info

node 22.23.2, darwin arm64
@vue/compiler-sfc 3.5.41
typescript 5.9

Any additional comments?

There is a second, independent problem in the same function's caller — tsConfigCache is an LRU
capped at 500 — which I am filing separately, since the fix for it is a capacity decision rather
than a one-line change.

The two patches

Our patch+118 −0
packages/compiler-sfc/__tests__/compileScript/resolveType.spec.tsindex ad066c7a0..aff0da987 100644@@ -1405,6 +1405,107 @@ describe('resolveType', () => {       expect(deps && [...deps]).toStrictEqual(['/src/types.ts'])     }) +    test('ts module resolve w/ project references sharing an extended base', () => {+      const files: Record<string, string> = {+        '/tsconfig.json': JSON.stringify({+          files: [],+          references: [{ path: './a/tsconfig.json' }, { path: './b' }],+        }),+        '/a/tsconfig.json': JSON.stringify({+          extends: '../tsconfig.base.json',+          include: ['**/*.ts', '**/*.vue'],+        }),+        '/b/tsconfig.json': JSON.stringify({+          extends: '../tsconfig.base.json',+          include: ['**/*.ts', '**/*.vue'],+        }),+        '/tsconfig.base.json': JSON.stringify({+          compilerOptions: {+            composite: true,+            paths: {+              '@shared/*': ['./shared/*'],+            },+          },+        }),+        '/shared/types.ts': 'export type Shared = { foo: string }',+      }+      const reads: Record<string, number> = {}+      const fs = {+        fileExists(file: string) {+          return !!(files[file] ?? files[normalize(file)])+        },+        readFile(file: string) {+          const key = normalize(file).replace(/\\/g, '/')+          reads[key] = (reads[key] || 0) + 1+          return files[file] ?? files[normalize(file)]+        },+      }++      const { props, deps } = resolve(+        `+        import { Shared } from '@shared/types'+        defineProps<Shared>()+        `,+        files,+        { fs },+      )++      expect(props).toStrictEqual({+        foo: ['String'],+      })+      expect(deps && [...deps]).toStrictEqual(['/shared/types.ts'])+      // both referenced configs extend the same base, which should only be+      // read and parsed once+      expect(reads['/tsconfig.base.json']).toBe(1)+    })++    test('ts module resolve w/ edited extended base after invalidation', () => {+      const files: Record<string, string> = {+        '/tsconfig.json': JSON.stringify({+          files: [],+          references: [{ path: './tsconfig.app.json' }],+        }),+        '/tsconfig.app.json': JSON.stringify({+          extends: './tsconfig.base.json',+          include: ['**/*.ts', '**/*.vue'],+        }),+        '/tsconfig.base.json': JSON.stringify({+          compilerOptions: {+            paths: {+              '@/*': ['./v1/*'],+            },+          },+        }),+        '/v1/types.ts': 'export type Props = { foo: string }',+        '/v2/types.ts': 'export type Props = { bar: number }',+      }+      const code = `+        import { Props } from '@/types'+        defineProps<Props>()+        `++      const first = resolve(code, files)+      expect(first.props).toStrictEqual({ foo: ['String'] })+      expect(first.deps && [...first.deps]).toStrictEqual(['/v1/types.ts'])++      // simulate editing the shared base config (e.g. during dev / HMR)+      files['/tsconfig.base.json'] = JSON.stringify({+        compilerOptions: {+          paths: {+            '@/*': ['./v2/*'],+          },+        },+      })+      invalidateTypeCache('/tsconfig.base.json')+      // also drop the configs extending it (the extends relationship itself+      // is not tracked by invalidateTypeCache)+      invalidateTypeCache('/tsconfig.json')++      const second = resolve(code, files, {}, '/Test.vue', false)+      expect(second.props).toStrictEqual({ bar: ['Number'] })+      expect(second.deps && [...second.deps]).toStrictEqual(['/v2/types.ts'])+    })+     test('ts module resolve w/ project reference folder', () => {       const files = {         '/tsconfig.json': JSON.stringify({packages/compiler-sfc/src/script/resolveType.tsindex 2d57438f1..67f237d9f 100644@@ -1079,6 +1079,16 @@ interface CachedConfig {  const tsConfigCache = createCache<CachedConfig[]>() const tsConfigRefMap = new Map<string, string>()+// Shared across loadTSConfig calls so that configs extending the same base+// (e.g. every package in a monorepo extending a shared tsconfig.base.json)+// reuse the already parsed parent instead of re-reading and re-expanding it+// for every config. Entries are keyed by TS on the resolved extended config+// path and store the merged result of that config's own `extends` chain, so+// an edit to any config in a chain can affect multiple entries; the whole map+// is therefore cleared in `invalidateTypeCache`.+// Note: parsed options derived from the same base are shared by reference and+// must be treated as read-only.+const tsExtendedConfigCache = new Map<string, TS.ExtendedConfigCacheEntry>()  function resolveWithTS(   containingFile: string,@@ -1193,6 +1203,9 @@ function loadTSConfig(     dirname(configPath),     undefined,     configPath,+    undefined,+    undefined,+    tsExtendedConfigCache,   )   const res = [config]   visited.add(configPath)@@ -1226,6 +1239,10 @@ export function invalidateTypeCache(filename: string): void {   tsConfigCache.delete(filename)   const affectedConfig = tsConfigRefMap.get(filename)   if (affectedConfig) tsConfigCache.delete(affectedConfig)+  // the extended config cache is keyed by TS-resolved paths and its entries+  // embed their parents' options, so a targeted delete could leave stale+  // descendants behind; clearing only costs a re-parse on the next load.+  tsExtendedConfigCache.clear() }  export function fileToScope( 
Merged fix · PR #15480+74 −0
packages/compiler-sfc/__tests__/compileScript/resolveType.spec.tsindex ad066c7a0..5b5df37c3 100644@@ -1405,6 +1405,63 @@ describe('resolveType', () => {       expect(deps && [...deps]).toStrictEqual(['/src/types.ts'])     }) +    test('ts module resolve parses a shared extended config once', () => {+      const base = '/tsconfig.base.json'+      const files: Record<string, string> = {+        '/tsconfig.json': JSON.stringify({+          files: [],+          references: [+            { path: './tsconfig.a.json' },+            { path: './tsconfig.b.json' },+            { path: './tsconfig.c.json' },+          ],+        }),+        [base]: JSON.stringify({+          compilerOptions: {+            composite: true,+            paths: {+              bar: ['./user.ts'],+            },+          },+        }),+        '/user.ts': 'export type User = { bar: string }',+      }+      for (const name of ['a', 'b', 'c']) {+        files[`/tsconfig.${name}.json`] = JSON.stringify({+          extends: base,+          include: ['**/*.ts', '**/*.vue'],+        })+      }++      // Counting reads of the shared base is what makes this test able to fail: the+      // traversal reaches three configs that extend it, and without a shared+      // `extendedConfigCache` each one re-reads and re-parses it.+      let baseReads = 0+      const { props } = resolve(+        `+        import { User } from 'bar'+        defineProps<User>()+        `,+        files,+        {+          fs: {+            fileExists(file) {+              return !!(files[file] ?? files[normalize(file)])+            },+            readFile(file) {+              if (normalize(file) === normalize(base)) baseReads+++              return files[file] ?? files[normalize(file)]+            },+          },+        },+      )++      expect(props).toStrictEqual({+        bar: ['String'],+      })+      expect(baseReads).toBe(1)+    })+     test('ts module resolve w/ project reference folder', () => {       const files = {         '/tsconfig.json': JSON.stringify({packages/compiler-sfc/src/script/resolveType.tsindex 2d57438f1..3f27fa578 100644@@ -1080,6 +1080,13 @@ interface CachedConfig { const tsConfigCache = createCache<CachedConfig[]>() const tsConfigRefMap = new Map<string, string>() +// `loadTSConfig` recurses through project references, so in a workspace where every+// package extends a shared base, that base is re-read and re-parsed once per config the+// traversal reaches - each parse allocating its own fully expanded options. TypeScript+// takes this cache as the 8th argument of `parseJsonConfigFileContent` and shares the+// parsed parents instead.+const extendedConfigCache = new Map<string, TS.ExtendedConfigCacheEntry>()+ function resolveWithTS(   containingFile: string,   source: string,@@ -1193,6 +1200,9 @@ function loadTSConfig(     dirname(configPath),     undefined,     configPath,+    undefined,+    undefined,+    extendedConfigCache,   )   const res = [config]   visited.add(configPath)@@ -1224,6 +1234,13 @@ export function invalidateTypeCache(filename: string): void {   fileToScopeCache.delete(filename)   fileToGlobalScopeCache.delete(filename)   tsConfigCache.delete(filename)+  // A changed config can be extended by any number of others and is cached under its own+  // resolved path, so there is no single entry to drop; clearing is cheap because this+  // only runs when a config file itself changed.+  if (filename.endsWith('.json')) {+    extendedConfigCache.clear()+    tsConfigCache.clear()+  }   const affectedConfig = tsConfigRefMap.get(filename)   if (affectedConfig) tsConfigCache.delete(affectedConfig) }