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
We use this library for rendering deploy logs at Netlify. When upgrading to 6.0.0, I've noticed that if one call to ansi_to_html detects an ansi value that should bold the text, that bold state carries over to subsequent calls to ansi_to_html.
I've created a CodeSandbox comparing 5.2.1 and 6.0.0 behavior. The first bold ansi value appears around the Netlify Build line. In 6.0.0, it bolds all subsequent lines while this doesn't happen in v5.
A workaround is to create a new instance of AnsiUp for every call.
The text was updated successfully, but these errors were encountered:
I had been observing the same statefulness in v5.2.1 as well, thought it to be working as intended. For example a unclosed color opening sequence carried over to subsequent ansi_to_html calls.
Hey there!
We use this library for rendering deploy logs at Netlify. When upgrading to 6.0.0, I've noticed that if one call to
ansi_to_html
detects an ansi value that should bold the text, that bold state carries over to subsequent calls toansi_to_html
.I've created a CodeSandbox comparing 5.2.1 and 6.0.0 behavior. The first bold ansi value appears around the
Netlify Build
line. In 6.0.0, it bolds all subsequent lines while this doesn't happen in v5.A workaround is to create a new instance of
AnsiUp
for every call.The text was updated successfully, but these errors were encountered: