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.
npm run develop gives TS Error about excessive stack depth
See original GitHub issueI get the error below when I run npm run develop on a fresh project setup.
It turns out the issue is related to the latest Typescript, but I though I would open this here so that others are aware if they should run into this issue.
https://github.com/typeorm/typeorm/issues/3194
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Why does this JSX cause an "excessive stack depth" error?
I am using Next.js' built in TypeScript (4.2.3) support to compile the following React component. const Component = (): JSX.Element ...
Read more >Errors | Node.js v19.3.0 Documentation
The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.
Read more >Error.prototype.stack - JavaScript - MDN Web Docs - Mozilla
The non-standard stack property of an Error instance offers a trace of which functions were called, in what order, from which line and...
Read more >JavaScript RangeError: Maximum Call Stack Size Exceeded
In case this error occurs due to an excessive number of function calls or variables, these should be reduced as much as possible....
Read more >Top 10 Most Common Node.js Developer Mistakes - Toptal
JavaScript in Node.js (just like in the browser) provides a single threaded ... code is running in production or in your local development...
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
That’s actually issue of typeorm. There is nothing to do on foalts part (except maybe shipping with previous version of typescript), wait for typeorm to fix it I’d say
https://github.com/typeorm/typeorm/issues/3194#issuecomment-526037271
Try this solution. Should work.