You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not something I think you really need in smaller applications, and adding logging for seriously big heavy-duty apps is not something loglevel is focusing on. Loglevel's a quick lightweight convenient solution, rather than a heavyweight kitchen-sink lib with every useful feature anybody can think of.
It's impossible to do without clobbering your stack traces; we currently just use bound console.X methods as properties on the log object (where possible), so loglevel doesn't run any code when you're logging, and your console output will show you exactly where the logging occurred. We can't do this if we also have to add any behaviour that occurs whenever a log method is called (as here).
The binding methods above means that in modern browsers you already get a specific file & line number that the message came from in the console, and if you're sensibly broken your modules into individual files this will give you equivalent information to what you're looking for anyway, I suspect.
I think your consideration is very reasonable. It's true that if you want to make loglevel very lightweight. Just want to confirm. Thank you for replying, Tim.
Hi Tim,
I am wondering if loglevel plan to support module logging like:
https://github.com/dingyonglaw/JSLog
Powpow.
The text was updated successfully, but these errors were encountered: