Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Type instantiation is excessively deep
See original GitHub issueI just upgraded from 2.5.0 to 2.6.5.
Typescript is not compiling.
My Code:
const logged_in = useStoreState(store => store.auth.get_login_status());
The message is
Type instantiation is excessively deep and possibly infinite
This was working fine earlier.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:32 (14 by maintainers)
Top Results From Across the Web
“Type instantiation is excessively deep and possibly infinite ...
Actual behavior: I'm getting this: Type instantiation is excessively deep and possibly infinite.ts(2589).
Read more >how to ignore "Type instantiation is excessively deep and ...
After update to Typescript 3.5 i'm getting a lot of "Type instantiation is excessively deep and possibly infinite.ts(2589)" errors.
Read more >TypeScript. Type instantiation is excessively deep and ...
Type instantiation is excessively deep and possibly infinite. How to fix. I've just started a migration to TypeScript. I see many unknown and...
Read more >Type instantiation is excessively deep and possibly infinite ...
Getting `Type instantiation is excessively deep and possibly infinite` errors whenever I pass MongoClient as a parameter in my code after ...
Read more >TypeScript - i18next documentation
Type error - excessively deep and possibly infinite ... If you face this issue whenever calling the t function: TS2589: Type instantiation is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ctrlplusb Seems resolved with
easy-peasy@3.0.0-alpha.2Thanks man!updating to v3.1.0 solved the issue for me