You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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. 👍
🚀 Feature Proposal
In case the output of
ts-jest
is channeled through Babel anyways, becausets-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.The text was updated successfully, but these errors were encountered: