Update @babel/code-frame

[nicolo-ribaudo]

Summary

There are some changes in how Babel emits ANSI colors. The rendered output is the same, but the sequences differ.

[netlify]

✅ Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	468b45d
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/65f978001e18e0000723063b
😎 Deploy Preview	https://deploy-preview-14976--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nicolo-ribaudo]

So, while opening this PR I caught a potential regression in Babel. There is no agreed-upon meaning on what FORCE_COLOR does: according to some it should always force color (https://force-color.org/), because NO_COLOR always unconditionally disables color and they are opposites. According to others, FORCE_COLOR=0 should disable colors.

Apparently Babel switched from one to the other, so I added this NO_COLOR=1 just to make sure that e2e tests aren't full of colors until when we decide what to do.

[SimenB]

👍

[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.