5.1.3 - RangeError: Maximum call stack size exceeded at inferFromTypes - Maybe Fixed with 5.2.0-dev.20230606

[jpwogaman]

Bug Report

🔎 Search Terms

• "RangeError: Maximum call stack size exceeded at inferFromTypes"
• "inferFromTypes"

🕗 Version & Regression Information

• This changed between versions 5.0.4 and 5.1.3
• Seems to be fixed when running npm install typescript@next //(5.2.0-dev.20230606)

💻 Code

npm run build

🙁 Actual behavior

Build error occurred
RangeError: Maximum call stack size exceeded
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:654
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:654
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11)
    at inferFromTypes (C:\***\node_modules\typescript\lib\typescript.js:65459:11) {
  type: 'RangeError'
}

🙂 Expected behavior

Build completed with no errors.

[dbrxnds]

Hi, we are also running into this issue on 5.1.3. Initially thought it was due to the size of our Prisma schema / types.

Not sure what I can do to help debug this, but willing to if anyone has ideas.

[paradoxloop]

We have this issue. too. Like @jpwogaman this is fixed for us by using a higher dev version of typescript:

npm install typescript@next //(5.2.0-dev.20230606)

[fatcerberus]

Nobody has a repro?

[AntQwanlity]

#54348

[janpio]

Here is another potentially related case: #54618
And I just commented there with a reproduction (Using Next.js, Prisma and Mongoose): #54618 (comment)

Update: I can confirm that typescript@5.2.0-dev.20230606 indeed fixes it. 5.2.0-dev.20230605 is still broken, but ..06 works.

[Jolg42]

With @janpio we could find that 5.2.0-dev.20230606 fixes the issue in mentioned reproduction.

I checked the changes that happened in 5.2 for that daily version I could see that
#54507 was backported to 5.1
#54538 was not backported yet

So it seems to me that this would be fixed once #54538 would be backported to 5.1?

[jakebailey]

The first PR should be enough to fix the crash. The second is a cleanup and potential perf boost (which we rarely backport).

This issue is really just a duplicate of #54348 which will be fixed in the next 5.1 patch (not yet released).

[suzan-rana]

Hi facing the same error using Next 13 app dir, prisma, typescript: 5.1.3, prisma: 4.15.0

[suzan-rana]

It worked guys.

[typescript-bot]

This issue has been marked as 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.