Recursion error logging React children (with hooks) about console-feed HOT 9 CLOSED

@samdenty I just created a PR for this ^

from console-feed.

Serializing logs with the current method is expensive, so when you call console.log, instead of sync blocking until the log has been dispatched, it delays it using setTimeout. Adding multiple todos, makes it block for longer.

Internally, replicator is currently used to serialize objects (so they can be transferred between DOM's), those stack frames are from within it.

The alternative way to handle recursion to use a two-way COM, which serializes objects as you expand them (the way chrome devtools does).

I haven't done this, as I've previously managed to get chrome devtools working embedded on a website using a mocked version of the devtools websocket API - giving you the real devtools, but I haven't put much time into that.

I don't currently have time to work on either, but pull requests are open

from console-feed.

You should be able to avoid the serializing / deserializing step, if the iframe is same-origin.

from console-feed.

In our own app (Framer) we get this error too, but there console-feed just lives in the same page (so no iframe like CodeSandbox). Any hints how we could avoid this error in that setup?

from console-feed.

Encode function should be removed

from console-feed.

Would you be interested in a PR to make this an option? Or should we fork the library for our use case?

from console-feed.

@koenbok PR would be ideal, something like Hook(console, cb, encode = true)

from console-feed.

Available in 2.8.8

from console-feed.

Thanks!

from console-feed.