Comments (1)
Loglevel is intentionally not going to do this: the goal is to be a simple wrapper around console.log
to let you control logging levels dynamically from your code, and to make it behave consistently across different platforms (so if something consistently fails everywhere when using console.log, then it should also fail when using loglevel).
You should do whatever you'd normally do when logging with console.log directly.
If you're seeing circular reference issues, that probably means you're using JSON.stringify, which can cause this. That's an issue in your code, see https://stackoverflow.com/questions/11616630/how-can-i-print-a-circular-structure-in-a-json-like-format for more details on how to deal with this. Alternatively, in most environments you can just pass data directly without stringifying it, and console.log
on your platform will probably do the sensible thing for you.
As a further option, you could create a plugin to handle this, by automatically stringifying content for you. I generally wouldn't encourage that, but if you'd like to be able to change global behaviour when logging then that's the way to do it: https://github.com/pimterry/loglevel#writing-plugins
from loglevel.
Related Issues (20)
- ESM - Angular 10 Tree Shaking Support? HOT 3
- Uncaught ReferenceError: _typeof is not defined HOT 2
- Only `log.info()` messages are output in `catch()` when the level is set to `info` HOT 3
- Dynamic Log level settings in Browser Console HOT 1
- GDPR: Add an option to disable cookie persistence HOT 4
- Is `console.log()` reference redefiend by loglevel? HOT 2
- Keep source(file:line) remain the same when methodFactory is been called. HOT 4
- log is not defined when attempting setLevel() in console HOT 3
- Programmatic log levels HOT 1
- Configurable persistence HOT 4
- methodFactory logLevel parametr has always same value HOT 2
- Show filename and line of logging code HOT 2
- Would you consider deprecating in favor of Roarr? HOT 2
- loglevel print duplicate log in React component HOT 5
- Is it possible to import Loglevel as an ES module in client-side javascript? HOT 5
- Possibility to save log output to file HOT 4
- current npm web page for loglevel shows no documentation at all HOT 3
- LogLevel output doesn't show when running in a test HOT 11
- LogLevel `trace`, `debug` and `info` not shown anymore on Google Chrome HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from loglevel.