Latest RC version tsc faild to load tsconfig.json>compilerOptions>types

[adoin]

When I run tsc on
"typescript": "^5.0.4",
It crash by "RangeError: Maximum call stack size exceeded".
Then I try
"typescript": "^5.1.1-rc",
It tell me tsconfig.json:20:16 20 "types": [ "vite/client","jest", "node"], ~~~~~~~~~~~~~ File is entry point of type library specified here.
So I remove "vite/client",
It works, but all type like styleValue can't be found.

What should I do? lower one crashed, higher one can read "types" config.
Any Idea or It's a issue?

[RyanCavanaugh]

Please provide a complete repro

[nopeless]

I am having similar issues, encountering it from Nuxt's development cli, sporatically. I'll get back if I ever find a reproduction

[adoin]

Please provide a complete repro

Not easy to make a repro, a make a clean project whick works fine...
I don't know which package or code crushed causing this problem.

[nopeless]

Update: it seems to only happen when vite hmr has been active for a long time. I don't know why this is the case but at least its reliable. Problem is reproducing takes like 20 minutes of waiting

[chrisahardie]

@RyanCavanaugh I'm able to repro on this project:

$ tsc --noEmit
error TS2688: Cannot find type definition file for 'vite/client'.
  The file is in the program because:
    Entry point of type library 'vite/client' specified in compilerOptions

  tsconfig.json:21:15
    21     "types": ["vite/client"]
                     ~~~~~~~~~~~~~
    File is entry point of type library specified here.


Found 1 error.

If I rollback to 5.0.4 the error disappears.

[sheetalkamat]

@chrisahardie the project you provided is configured incorrectly. "typeRoots" is a place where the types should be looked up and "types" is the list of types to automatically add to project. So configuring "typeRoots": ["./app/ui/types/custom.d.ts"] is trying to resolve @vite/client from that location which seems not intentional

[chrisahardie]

@sheetalkamat thanks, I've inherited a tsconfig and didn't catch the misconfiguration. I assume that between latest and version 5.0.4 things have simply tightened up.

[microsoft-github-policy-service]

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

[microsoft-github-policy-service]

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