webstorm debug maximum call stack size exceeded

Export `registerConsoleShortcuts` from `vitest/node` - ) in | Package | Change | Age | Adoption | Passing | Confidence | This is reproducible with this stackblitz: stackblitz System Info ❯ start node_modules/vitest/dist/cli.js:105:17 Reproduction ❯ startVitest node_modules/vitest/dist/:22440:5 ❯ Vitest.start node_modules/vitest/dist/:15291:5 ❯ Vitest.report node_modules/vitest/dist/:15571:5 ❯ DefaultReporter.onFinished node_modules/vitest/dist/:12212:17 ❯ DefaultReporter.onFinished node_modules/vitest/dist/:10898:16 ❯ DefaultReporter.reportSummary node_modules/vitest/dist/:11037:16

❯ DefaultReporter.printErrorsSummary node_modules/vitest/dist/:11111:18 ❯ DefaultReporter.printTaskErrors node_modules/vitest/dist/:11166:29 ❯ Logger.printError node_modules/vitest/dist/:14026:12 ❯ printError node_modules/vitest/dist/:13811:3

❯ printErrorMessage node_modules/vitest/dist/:13922:18 ❯ Object.red node_modules/picocolors/picocolors.js:17:13 ❯ replaceClose node_modules/picocolors/picocolors.js:25:30 RangeError: Maximum call stack size exceeded However, in this case, the use of picocolors in displaying the error causes a stack overflow: This is a common use case because react-testing-library usually restricts its output and it's hard to see where in the DOM an issue exists. I've set the DEBUG_PRINT_LIMIT env var to 100000.I'm importing a large external library (ag-grid) that I know causes massive DOMs.Note the following changes I've made in this stackblitz in order to get a huge output to trigger this: This is reproducible with this stackblitz: stackblitz The source-map-support version I have in my project is 0.5.19.When there are very large outputs, picocolors causes a stack overflow. (/Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:166:26)Īt /Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:65:24Īt mapSourcePosition (/Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:196:21)Īt wrapCallSite (/Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:377:20)Īt Function.prepareStackTrace (/Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:426:39)Īt maybeOverridePrepareStackTrace (internal/errors.js:87:29)Īt prepareStackTrace (internal/errors.js:66:5)Īt (/Users/leandrocolodete/my-project/node_modules/mocha/lib/cli/run.js:321:31) I am using RubyMine, and this is the command line that starts the debug session: /Users/leandrocolodete/.nvm/versions/node/v12.18.3/bin/node -inspect-brk=57678 /Users/leandrocolodete/my-project/node_modules/mocha/bin/_mocha -require ts-node/register -timeout 0 -ui bdd -reporter '/Users/leandrocolodete/Library/Application Support/RubyMine2018.3/NodeJS/js/mocha-intellij/lib/mochaIntellijReporter.js' /Users/leandrocolodete/my-project/src/tests/controllers/ExaaSController_test.ts -grep '^my test$'ĭebugger listening on ws://127.0.0.1:57678/4c98c066-b365-4648-ab7c-e39fbab84aecĪ few seconds later, mocha exits and I can see the following stack trace: RangeError: Maximum call stack size exceededĪt retrieveSourceMapURL (/Users/leandrocolodete/my-project/node_modules/source-map-support/source-map-support.js:154:21)Īt Array. I’ve been having the exact same problem when debugging a TypeScript mocha test.

Webstorm debug maximum call stack size exceeded