is there a simple way to just use signale as a drop in replacement for the usual terminal log? i am not sure if i really want to write a custom logger for this.
@mxmzb yep, since 1.1.0 the signale.log() logger, that behaves the same as console.log(), is available : ) Original issue thread #4
In a similar vein to the above, would you welcome a PR which adds a stream property to the type object which lets you override stream at a type-level? so that error types could go to process.stderr
one nasty thing about that approach though is that 'types' is no longer 100% serializable to the package.json but if thats an issue i can just create some string to stream mapping
@jordrake maybe you could write a plugin / wrapper that does this on top of a signale instance?
I'm experimenting with ways to add hooks around the loggers, since I wanted to be able to filter out certain log levels depending on a threshold. seems like these kinds of hooks could also be used to make a logger use a different stream maybe?
I'll share a gist once I clean up what I've been doing :sparkles:
Support for multiple streams & optional streams per logger added on #27
Contributions are always super welcome : )
@brettimus happy to help out any moment :smile:
much appreciated! also props to @jordrake -- pretty cool to go from "this would be nice" to "merged" in just a few hours!
@klauscfhq#35 could be nice feature
@klauscfhq Hi Klaus, what’s that nice console in the Signale docs?
@rjoydip Yep, indeed it would be an interesting addition : )