6 ms·
Show HN: Universal Logger for Node, Deno, Bun, Browser
Hey everyone,
I had posted about my project https://adzejs.com https://adzejs.com a couple of years ago and it was met with a lot of interest, so I'm writing about the major v2 update that's just been released to see if anyone is interested.
What makes Adze interesting compared to other logging libraries like pino, bunyan, winston, etc?
Adze is universal. This means that Adze will "just work" in all of your environments. This is especially handy when working with SSR projects like sveltekit, nuxt, next, etc. You can also use Adze with Bun or Deno without any special adaptations or considerations.
Adze 2.x is also smaller (13.29kb minified and brotlied) and faster than the original. Benchmarks put it at generating 100,000 logs in ~700ms.
Version 2 also offers a cleaner API than version 1 as it no longer uses factories and instead uses static class methods.
import adze from 'adze';
// Generating a log
adze.timestamp.ns('foo').log('A log with a timestamp and namespace.');
// Making a child logger
const logger = adze.timestamp.ns('foo').seal();
logger.log('A log with a timestamp and namespace.');
Adze 2.x comes with support for four different types of log formats out-of-the-box. These formats include:
- a human-readable pretty format - a machine-readable JSON format that is compatible with the Bunyan CLI - a format for common logs - and a format for simple stdout logging
Adze 2.x also offers better extensibility support. You can now create custom formatters and custom middleware for modifying log behavior or transporting them to another source (like a file, etc). Log listeners are also still supported.
Changing formats is easy.
import adze, { setup } from 'adze';
setup({
format: 'json', // <- Change with an env var
});
adze.withEmoji.success('This is a pretty log!');
Adze 2.x also includes a handy new template literal logging feature for times where you are repeating logs frequently with slightly different messages (like error messages in a catch). Adze offers a new sealTag terminator that will seal your configuration into a template literal tag function to further simplify your logging.
Example
import adze from 'adze';
// Let's create a reusable ERR tag with emoji's, timestamps, and the "my-module" namespace.
const ERR = adze.withEmoji.timestamp.ns('my-module').sealTag();
try {
// do something that could fail...
} catch (e) {
ERR`Printing my error as an error log! ${e}`;
}
There is much, much more to Adze than what I can present in this post, but please check it out at https://adzejs.com https://adzejs.com and let me know what you think! Try it out!
Also, please give it a star to bookmark it at https://github.com/adzejs/adze https://github.com/adzejs/adze if you might use it in the future!
I appreciate any feedback as well. This has been a huge labor of love for me and I hope it benefits you all as well.
Thank you!
- SahAssar 2y ago> Adze is universal. This means that Adze will "just work" in all of your environments I'm not sure what this means. console.log is also universal (at least for the platforms mentioned), do you mean that client side logs are shipped to the server?
- difosfor 2y agoI guess it provides a complete console like API in all cases where some environments offer fewer console methods?
- SahAssar 2y agoI'm pretty sure all the mentioned runtimes support all the standardized console methods, and it does not mention anything about compatability with more restricted environments like quickjs or embedded js.
- ajstacy06 2y agoIt's universal meaning it works in the web browser and the backend without any configuration. All other loggers work in one or the other, or if they work in both the functionality is severely limited. Winston and Bunyan only work server side because they use node fs streams. Pino is primarily designed to be a server side library, but it can run in the browser by using browserify and using limited funcionality. Of course console methods are universal. This library isn't providing console methods, it's providing enterprise/production level functionality on top of the console. If you want to use Winston in Sveltekit or the like, you have to wrap browser checks around parts of it, otherwise it will explode when bundled.
- SahAssar 2y agoRight, I usually prefer to use the built in console methods with some currying when needed so I might not be the audience. This has worked well enough even for "enterprise" use-cases. If I may give one suggestion maybe drop the dependency on 'vuepress-plugin-search-pro' (48MB) and maybe 'date-fns' (23MB), that seems like some really large dependencies that might not be required.