Add a recursion limit to improve stack overflow errors

🔍 Search Terms

"recursion", "recursion limit", "stack overflow"

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

It would be nice to have a recursion limit that allows a better error message in stack overflow errors like these, and that could potentially include more context about the recursive function.

📃 Motivating Example

This VS feedback item that shows how the error surfaced to the user is quite overwhelming.

💻 Use Cases

1. What do you want to use this for? Debugging/fixing stack overflow errors.
2. What shortcomings exist with current approaches? The error lists/output panes in editors aren't great at displaying huge stacks like these.

No implementation files, tests, or entry points are named. Start by reviewing the linked Visual Studio feedback and the TypeScript compiler's current stack-overflow handling, then determine the scope and design of a recursion limit. Done should include a better diagnostic with useful recursive context without changing existing JavaScript behavior.