Huge amounts of debug output emitted

[starpit]

Hiya. We are attempting to upgrade from react-markdown v5 to v7. This upgrade seems to have pulled in a version of micromark that emits a huge amount of debug output. I mean hundreds of thousands of lines of debug. I usually run with localStorage.debug='*' when developing, which means that micromark slows things down hugely. Here are some examples

micromark main: passing `96` to start +0ms
micromark position: restore: `{"line":15,"column":1,"offset":1013,"_index":21,"_bufferIndex":0}` +0ms
micromark main: passing `96` to start +1ms
micromark enter: `codeFenced` +0ms
micromark enter: `codeFencedFence` +0ms
micromark enter: `codeFencedFenceSequence` +0ms
micromark consume: `96` +1ms
micromark main: passing `96` to sequenceOpen +0ms
micromark consume: `96` +0ms

This is mostly an FYI, i guess, because one can always use

localStorage.debug="*,-micromark"

but it seems odd to have such a huge amount of debug on without some extra flags?

[ChristianMurphy]

Thanks for reaching out, sorry you ran into a spot of trouble.

The verbose logs are hidden behind two flags. https://github.com/micromark/micromark#size--debug

1. one is an export condition which only is used in a development environment
2. the other a debug package logging flag

In your example, both the export condition and the log level have been set to be verbose.

If you don't want verbose debugging in development localStorage.debug="*,-micromark" could be a good option.
It will also not log when the export condition/environment changes to production.

[starpit]

Thanks for the kind reply. Yes, the -micromark is an adequate workaround. The downside is that we now need to add an important warning to our developer docs. I wish the debug npm had some support for debug levels. This extreme level of debug output would normally be relegated to a "SILLY" debug level. But we work with what we got!