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

@hiryus-org/tracer

v1.1.26

Published

Simple logger.

Downloads

39

Readme

Installation

npm install @hiryus-org/tracer

Usage

// Import library
const tracer = require('@hiryus-org/tracer');

// By default, event message is output as text on the console for all default
// levels (fatal, error, warning, info, debug, trace and access).
// See "configuration" section to change it.

// The log event, you can use the log() function:
// tracer.log(level, message, [metadata])
tracer.log('info', 'application started');
tracer.log('access', 'GET /article/157', { ip: '127.0.0.1' });

// There are also shortcuts for the default log levels.
// Metadata is facultative too.
tracer.fatal('message', { foo: 'bar' });
tracer.error('message', { foo: 'bar' });
tracer.warn('message', { foo: 'bar' });
tracer.info('message', { foo: 'bar' });
tracer.debug('message', { foo: 'bar' });
tracer.trace('message', { foo: 'bar' });
tracer.access('message', { foo: 'bar' });

Configuration

const tracer = require('@hiryus-org/tracer');

tracer.loggers.clear(); // to remove defautl loggers
tracer.loggers.add({
    levels: ['fatal', 'error'],
    type: 'console',
    format: 'text',
});
tracer.loggers.add({
    levels: ['fatal', 'error', 'warning', 'info', 'debug', 'trace'],
    type: 'file',
    format: 'json.raw',
    path: 'application.log',
});

// or in one go:

tracer.loggers.set([{
    levels: ['fatal', 'error'],
    type: 'console',
    format: 'text',
}, {
    levels: ['fatal', 'error', 'warning', 'info', 'debug', 'trace'],
    type: 'file',
    format: 'json.raw',
    path: 'application.log',
}]);

Formats

  • text: outputs each event message as a text line (metadata is ingored for this format)
  • json.raw: outputs each event as a JSON string, one event per line (and thus, without indentation)
  • json.pretty: outputs each event as a JSON string with indentation and line breaks

Test

  • To launch tests, just run npm run test.
  • To gather coverage data, run npm run coverage. Coverage reports are in the coverage directory.

Contribute

See doc/contributing.md