[Bug]: RangeError: Maximum call stack size exceeded

[shafqatalix]

Version

v28.0.0-next.2

Steps to reproduce

Tests pass with "ts-jest/legacy" preset but fails on "ts-jest" only preset.

Expected behavior

Pass with "ts-jest" only

Actual behavior

Fail tests with following error.

Debug log

Additional context

No response

Environment

MAC, 
NodeJS 16.x
Jest 28.0.2

[ahnpnl]

Do you have a reproduce repo for this?

[benasher44]

This happens to us as well. I added some logging, and this issue happens as soon as ts-jest encounters a huge codegenerated file. It'd be great if there was a way to get ts-jest to skip that file? I'm not sure if it can skip that file in the related function in hoist-jest though, since I'm not sure what it's doing

[ahnpnl]

Currently there is no way to skip the file because the transformer is processed during compilation process. One option is passing to the transformer an option to tell it to skip execution.

[benasher44]

Gotcha. Is it possible to rewrite sortStatements to not use recursion? I think for large files, that might be the only way out.

[benasher44]

I converted sortStatements locally to use Array.sort, and it seems to work:

var sortStatements = function (statements) {
        if (statements.length <= 1) {
            return statements;
        }
        return statements.sort((a, b) => isHoistableStatement(a) && !isHoistableStatement(b) && !isJestGlobalImport(b) ? -1 : 1 )
    };

I'm not 100% sure I got the sort function right. What do you think?

[ahnpnl]

Would you pls trying out a PR with a scenario you have and the purpose solution? We have tests for hoisting so if you add your case in and we can easily check

[benasher44]

Yep! I'm having a bit of trouble coming up with a way to make a setup that has enough imports that also doesn't involve exposing our whole project. Would it be sufficient to replace this with Array.sort and have it use existing tests? Feels like a reasonable improvement on its own (not having to maintain your own sort).

[benasher44]

Opened a PR that should at least validate that this passes existing tests (needs approval to start the test run). I hope it's okay that I don't have a special test case file to go along with it. Hopefully you agree using Array.sort will bring its own maintainability benefits 🙏

[gregveres]

Is there a way to get this ported back to a 27 version?
I am seeing this too but I am stuck on jest 27 because the tool chain I rely on (vue 2) is still on v27 of jest tools.

[ahnpnl]

Sure we can backport that