Global functions: add pretty error for syntax error.

[binygal]

Provide explanation that configuration transform entry is not working
on the global functions.

Summary

Right now Jest is not running transformation on setup and teardown global functions and this is confusing for the users, this PR prettify the error message on syntax error to note that transform is not supported in global functions. (#5164)

Test plan

Check that the new copy is actually printed to the screen as can be seen in the provided screenshots.
(2 tests added, using an invalid globalSetup and globalTeardown, and matching the process stderr against a regex with the "not supported" copy)

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@66560c3). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #6901   +/-   ##
=========================================
  Coverage          ?   66.92%           
=========================================
  Files             ?      250           
  Lines             ?    10383           
  Branches          ?        4           
=========================================
  Hits              ?     6949           
  Misses            ?     3433           
  Partials          ?        1

Impacted Files	Coverage Δ
packages/jest-cli/src/runJest.js	64.21% <0%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 66560c3...600ffe4. Read the comment docs.

[SimenB]

This loses the if SyntaxError part of the error, as well as the file name and line. We should keep that info as well

[SimenB]

Played around locally:

Not sure I'm happy with it...

[binygal]

@SimenB Do you think the approach of better message on error is wrong?

[SimenB]

@binygal sorry about not responding earlier.

I do think providing a better message is the right thing to do, but your current approach removes the syntax error itself making it harder for the user to track down their error.

My local playing around (that I don't think I have available anywhere anymore) basically re-added the information that was lost, and added a code frame. If you can accomplish something like that'd, I'd love to merge it 🙂

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.