npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ratlog

v1.0.3

Published

application logging for humans and machines

Downloads

26

Readme

🐀 Ratlog JavaScript library

Application Logging for Rats, Humans and Machines

Build Status npm GitHub last commit GitHub issues

Ratlog.js is a JavaScript logging library that supports the Ratlog logging format.

The output is opinionated to be readable by rats, humans and machines.

The provided API is designed to be as simple to use as possible while providing you with all Ratlog semantics. Each log line can consist of a message, tags and fields which provides you enough context to quickly understand what's happening in your system.

For an introduction, see this article. To learn more about the design and ideas behind the Ratlog spec, checkout ratlog-spec.

The Ratlog JavaScript provides Ratlog semantics and the Ratlog format but they can be used independent from each other:

If you only want to make use of the API semantics, you can create a logger using ratlog.logger() and use JSON or any other format as output. This way you can combine Ratlog's logging semantics with your logging framework or service of choice.

For more have a look at the API Documentation.

Getting started

Install the ratlog NPM package:

npm i ratlog

Starting logging:

const ratlog = require('ratlog')
const log = ratlog(process.stdout)

log('hello world')
// => hello world

// Add fields
log('counting', { count: 1 })
// => counting | count: 1

// Add fields and a tag
log('counting', { count: -1 }, 'negative')
// => [negative] counting | count: -1

// Create another logger bound to a tag
const warn = log.tag('warning')

warn('disk space low')
// => [warning] disk space low

// Combine and nest tags any way you like
const critical = warn.tag('critical')

critical('shutting down all servers')
// => [warning|critical] shutting down all servers


// Create a mock logger while testing
const logHandler = jest.fn()
const testLog = ratlog(logHandler)
testLog('hi', 'info')
expect(logHandler).toBeCalledWith('[info] hi\n')

There are more examples to learn how you can use tags to provide context in your logs about different components of your system.


Thanks to @wmhilton for pointing this out:

You can color tags by combining Ratlog with chalk:

const warn = log.tag(chalk.red('warning'))
log('Normal log')
warn('Warning log')

colored log tags

Requirements

Node >= 8.0.0

Development and Contributing

Feel free to open an issue to ask questions or give feedback and make suggestions.

To contribute code, run npm i to setup your dev environment and before submitting a Pull Request, make sure npm t is passing.

License

MIT