Neville Franks

Thanks for that. Making it Sponsor only is smart. Re. Doc generators. I've not tried these: https://www.gitbook.com/ seems quite popular. https://readme.com/ looks interesting. https://docsify.js.org/ is another.

@alfonsocuccaro I suggest you have a close look at [YJS](https://yjs.dev/) which I'm using in a new app and it is amazingly good, close to magic. Also on [Github](https://github.com/yjs/yjs) and Discord...

@odama626 Yes when Gun first came out I also thought it was interesting and potentially useful. However I was always concerned about it being called a Database and was written...

Ok. It is interesting that I've come along after the fact and suggested something that was in place earlier. That would suggest there was and possibly still is a need....

Yes, I'm using [ansicolor](https://github.com/xpl/ansicolor) which replaces your ansi code. Works a treat. I now have a combined human and browser module called _superHuman_ 😀 which has target _(browser/node)_ options amongst...

Either approach seems fine _(or even both)_ but ```logWithMetadata()``` is probably clearer. I use a separate tag/metaData for each source file. ie. all logger calls in a given source use...

Thinking about these approaches over night and one thing that came to mind is I wouldn't want to have to create a wrapped ```logWithMetadata()``` for each ``level`` for different ``tag/metaObj``....

Ok, after working on caterpillar most of the day I'm now leaning towards ```logger.log(new Metadata({..}), .. )``` versus _introducing_ a new function. And just your third example: ```` logger.log(new Metadata({tags:...

In this case should it return a falsey result or ``null``. ``Transform.write()`` checks for null, but will pass false on which doesn't seem right.

I think this should be optional as not everyone wants the added overhead of codemirror. I also tried the page you linked to, selected Javascript and pasted some JS and...