Open Source JavaScript Logging Software

Fancy output with fallback for minimal environments. Consistent command-line interface (CLI) experience. Spam prevention by throttling logs. console uses std in the underlying so calling wrapStd redirects console too. The benefit of this function is that things like console.info will be correctly redirected to the corresponding type. Any instance of consola that inherits the mocked instance, will apply provided callback again. This way, mocking works for withTag scoped loggers without the need for extra effort. Choose between one of the built-in reporters or bring in your own one. By default FancyReporter is registered for modern terminals or BasicReporter will be used if running in limited environments such as CIs. A reporter (class or object) exposes log(logObj) method. To get more info about how to write your own reporter, take a look at the linked implementations.

Hackable and configurable to the core, signale can be used for logging purposes, status reporting, as well as for handling the output rendering process of other node modules and applications. You can now support the development process through GitHub Sponsors. To create a custom logger define an options object yielding a types field with the logger data and pass it as argument to a new signale instance. By utilizing the secrets option, secrets and other sensitive information can be filtered out from the body as well as the metadata, i.e. scope names etc, of to-be-logged messages. The option is part of the configuration object passed to a Signale instance on its initialization, and is of type Array<String|Number>. The array can hold multiple secrets, all of which are removed, if present, from the to-be-logged messages and are replaced with the default '[secure]' string.