Support errors with messages containing ANSI color code

[Mumeii]

🤔 What's the problem you're trying to solve?

Hello 👋

I've started to use Cucumber-js with its default HTML reporting tool

In order to have a more flexible assertions, I'm also using Jest's expect as well as jest-extended

Both of those assertion modules are throwing exceptions with messages that contains ANSI colore code characters

Unfortunately, those characters don't seems to be handled the right way, as those codes are not taken into account to highlight the text with the right color, but instead are displayed as is.

See this screen shoot example :

Someone form the help-js channel of Cucumber's Discord advised me to create a feature request here about this trouble

✨ What's your proposed solution?

Also have the React analyzing the error messages, and have each of the ANSI color codes turned into a corresponding block to have the text colorized the right way ?

Maybe it would necessitate to change the way the background color is managed on such error message display, else I guess that a red colored text displayed over a red background would be quite unreadable

As the coloring of such tools is most of the time targeting terminals with black background, maybe it would be better to have error messages simply surrounded by a red frame, but displayed over a black background ?

⛏ Have you considered any alternatives or workarounds?

Except using another HTML reporting tool, I've also considered the following :

• catch the exceptions thrown by expect, and perform the stripping of color codes from the message before rethrowing it
• add an extra step in my CI in order to apply a transformation on the produced HTML file(s) myself
• create a PR myself to solve this problem, but I didn't knew in which Cucumber's github repository I had to do it, and since I've learned it's related to current repository, as I'm not familiar at with React coding, I prefer simply creating the issue 😛

But none of those solutions are really appealing 😢

📚 Any additional context?

No response