-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Maximum call stack size exceeded at [email protected] and @next #28785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Is your code really "heavy" on generics? [EDIT] I ask because I have projects with a lot of.. Err.. Complex generic types and they failed when I tried to upgrade. I took that as an opportunity to rewrite the projects, though. |
I'm getting this as well for a project that is heavy on generic types. |
After a thorough investigation I found that it is one of my dependencies that's causing the issue. If the issue reported here is not relevant it can be closed. |
Is it possible that extending and adding the same generic default causes the crash?
I'm taking about this: |
I haven't been able to build a small reproduction yet, but lodash typings definitely seem to be a large contributor (~4.14.90+). Removing them works around the stack out for us—but it only occurs in some of our more complicated projects |
@sandersn we at least need a root cause here before 3.4 goes out |
This is fixed in 3.3.3333. |
After installing typescript 3.2.1 I'm getting this error:
I also tried with typescript@next getting the following:
Related Issues:
I found similar issues:
#16533
#15926
But I am confident I'm not doing any circular reference.
The solution was compiling successfully before upgrading to [email protected]
My tsconfig.json:
My package.json:
The text was updated successfully, but these errors were encountered: