RangeError: Maximum call stack size exceeded when building monaco (5.5.2) #59253
Assignees
Labels
Bug
A bug in TypeScript
Crash
For flagging bugs which are compiler or service crashes or unclean exits, rather than bad output
Domain: JS Emit
The issue relates to the emission of JavaScript
Fix Available
A PR has been opened for this issue
Fixed
A PR has been merged for this issue
Milestone
Comments
The error: |
|
|
Also, this goes away if you drop the config for |
DanielRosenwasser
added
Bug
|
Huh, funny. Two things I wanna do then:
|
|
So, weirdly enough, this is fixed in In any case, that makes this "fixed", but to my second point above, I've opened #59398 with the fast bail-outs to avoid the reference walking pass in some common cases that don't need it. @DanielRosenwasser this is scheduled for a patch release, but #59183 seems like an odd change to port, being a behavioral change - how do you feel about this? |
weswigham
added
Fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔎 Search Terms
"maximum call stack size"
🕗 Version & Regression Information
⏯ Playground Link
No response
💻 Code
Not sure which code causes the crash.
🙁 Actual behavior
When compiling monaco-editor with [email protected] or higher, it will result in a
Maximum call stack size exceeded.npm run build-monaco-editor(this will work as it uses [email protected])npm install [email protected]npm run build-monaco-editoragain (this will fail)🙂 Expected behavior
When compiling
monaco-editorwith the latest TypeScript, I shouldn't be seeing aMaximum call stack size exceeded.Additional information about the issue
No response
The text was updated successfully, but these errors were encountered: