Maximum call stack size exceeded

🔎 Search Terms

call stack exceeded

🕗 Version & Regression Information

• This changed between versions 5.8.3 and 5.9.2
• This changed in commit or PR _______
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
• I was unable to test this on prior versions because _______

⏯ Playground Link

No response

💻 Code

// Your code here

🙁 Actual behavior

We noticed that there's a potential regression between the versions 5.8.3 and 5.9.2.

When allowing Dependabot to bump from 5.8.3 to 5.9.2, we started seeing the yarn astro check command failing with the following output:

🤟 ~/Sites/[project] (dependabot/npm_and_yarn/dev/typescript-5.9.2): yarn astro check          
19:42:18 [content] Syncing content
19:42:18 [content] Synced content
19:42:18 [types] Generated 103ms
19:42:18 [check] Getting diagnostics for Astro files in project...
Maximum call stack size exceeded
  Location:
    [project]/node_modules/typescript/lib/typescript.js:3371:46
  Stack trace:
    at String.replace (<anonymous>)
    at getCanonicalFileName ([project]/node_modules/typescript/lib/typescript.js:129084:17)
    at toPath3 ([project]/node_modules/typescript/lib/typescript.js:127606:12)
    at findSourceFile ([project]/node_modules/typescript/lib/typescript.js:128749:20)
    at findSourceFile ([project]/node_modules/typescript/lib/typescript.js:128749:20)

🙂 Expected behavior

I would expect the yarn astro check command to succeed with hopefully no type issues since nothing else was changed in the PR other than the version being bumped.

Additional information about the issue

No response

首先，使用报告中的 yarn astro check 命令，在 TypeScript 5.8.3 和 5.9.2 下重现该失败。检查 node_modules/typescript/lib/typescript.js 中 stack trace 的位置，尤其是 getCanonicalFileName、toPath3 和 findSourceFile；确定回归问题并使 check 能够在不出现 maximum call stack 错误的情况下完成，即表示完成。