At the moment there’s a lot of “clutter” in what is logged; it seems to all just use console.log which counts under the “info” category. And means anything the creator logs for their own “real” debugging is much harder to see–especially with more complex generators with many imports and nested imports.
If debug was used instead, the creator could choose to see all those things by turning on the “verbose” category in their dev tools. Or leave it off, and see the “info” channel with their own logs very easy to see and much more useful.
console.debug()? Hmm, never heard of this before. Thanks to this post I immediately learnt what it does.I am unlocking many new JavaScript capabilities this month! 😄
Yeah interesting isn’t it? I knew there was this “verbose” category but not what counted as it.
There’s also
console.info()you can use to explicitly send to the “info” category. Andconsole.warn(), andconsole.error().
Today I learned - thanks! I was thinking about how annoying all the internal/plugin logs were recently, but didn’t know about
console.debug(I was going to fix via alocalStorageflag). Let me know if there are any stray logs that I’ve missed in the engine, or commonly used plugins.I’ve kept ai-text-plugin input logging for each generation request, since I use that all the time (to make sure I’ve not made any mistakes constructing my prompt), so I assume others will find it useful too.
Great–I’m so happy! :D
I’ll bookmark this comment and come back to let you know if I spot more logs that should be
.debug()Cool, will do 👍
