Make warning message for nodejs ts target version mismatch configurable

[herschel666]

🚀 Feature Proposal

In case the output of ts-jest is channeled through Babel anyways, because ts-jest is an optional part of the Jest setup, the warning message regarding a mismatching nodejs target doesn't really make sense. In this case it would be nice to have an option to disable it.

Motivation

My team and I are maintaining Hops, which ships with a Jest-preset. This again contains the optional ts-jest (mentioned above) and will always run the code through Babel. So this warning is unnecessary and confusing for users of Hops.

[ahnpnl]

The warning message was fixed in #1729 which is in 26.1.1 . Or I understood your case is different ?

[herschel666]

Sorry. Just checked again with the project, that showed the warning, and it turned out that there's been a misconfiguration with the custom Jest preset, so that the babelConfig-option got lost. After fixing that, the warning disappeared. 👍