It seems a lot of thought was put into the design of LogTape. I may integrate my logging tool with LogTape. My tool needs the callsite, so I don't think I can just write a LogTape sink; I think it would also have to wrap/extend LogTape itself.
- Automatic namespaces based on calling function + path to source filename/path.
- Can be inserted into the middle of expressions.
- Can output a link that opens the file in your editor/IDE of choice.
- Simple to disable
- Diagnostics/hints to help with installation/configuration
---
I was surprised by the amount of logs already being output (by Vite) when I simply added https://github.com/debug-js/debug to my project.
Fortunately, debug-js output is very simple to filter via ENV and/or localStorage.debug
---
What I look for in a logging library (with more focus on dev/debugging than production):
- Easy to add new logs.
- Easy to identify the location of the code that triggered the log. I noticed a lot of my logging was simply to indicate the start and maybe end of a function call. If needed, I might add additional logs between these.
- Easy to surgically disable/filter groups of logs. Should be easier than commenting/uncommenting calls to logger. Otherwise I end up with lots of uninteresting log chatter (or I delete log statements, only to add them again later...)
---
I built a DX-focused logging library on top of debug-js. Notable features of https://github.com/Leftium/gg:
- Automatic namespaces based on calling function + path to source filename/path.
- Can be inserted into the middle of expressions.
- Can output a link that opens the file in your editor/IDE of choice.
- Simple to disable
- Diagnostics/hints to help with installation/configuration
---
I was surprised by the amount of logs already being output (by Vite) when I simply added https://github.com/debug-js/debug to my project.
Fortunately, debug-js output is very simple to filter via ENV and/or localStorage.debug
---
What I look for in a logging library (with more focus on dev/debugging than production):
- Easy to add new logs.
- Easy to identify the location of the code that triggered the log. I noticed a lot of my logging was simply to indicate the start and maybe end of a function call. If needed, I might add additional logs between these.
- Easy to surgically disable/filter groups of logs. Should be easier than commenting/uncommenting calls to logger. Otherwise I end up with lots of uninteresting log chatter (or I delete log statements, only to add them again later...)