You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm an avid user of this package for all our projects. It really helps us level up our skills with regards to TypeScript.
However, we do have some issues, and I'm not sure how they can be resolved.
For complex sites and queries, we often encounter this Type instantiation is excessively deep and possibly infinite. error. This error is frustrating because it seems somewhat random where it shows up in the editor and whether or not it actually returns an error when compiling the TypeScript.
Furthermore, (and perhaps this is related) on larger projects, the editor slows down due to ESLint and the compilation process itself, with type-checking that can take more than 3 minutes.
I'm not sure if this is something that's easily solvable, or if we are just pushing TypeScript to its limit. Either way, I wanted to bring this up to start a discussion about possible solutions.
We are separately testing doing "manual groq + zod" and these problems does not show up.
The text was updated successfully, but these errors were encountered:
Closing, as this is likely fixed by the 1.0 release. See #58 for a similar issue, which is no longer reproducible with 1.0.
If this issue is still reproducible, please open a new issue. Thank you!
Hi!
I'm an avid user of this package for all our projects. It really helps us level up our skills with regards to TypeScript.
However, we do have some issues, and I'm not sure how they can be resolved.
For complex sites and queries, we often encounter this
Type instantiation is excessively deep and possibly infinite.
error. This error is frustrating because it seems somewhat random where it shows up in the editor and whether or not it actually returns an error when compiling the TypeScript.Furthermore, (and perhaps this is related) on larger projects, the editor slows down due to ESLint and the compilation process itself, with type-checking that can take more than 3 minutes.
I'm not sure if this is something that's easily solvable, or if we are just pushing TypeScript to its limit. Either way, I wanted to bring this up to start a discussion about possible solutions.
We are separately testing doing "manual groq + zod" and these problems does not show up.
The text was updated successfully, but these errors were encountered: