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

trk-log

v0.1.16

Published

Helps logging stuff - ALPHA

Downloads

37

Readme

Just:

var trk = require('trk-log').init(settings);

Where: settings is an optional object with various settings (since under development), including:

  • app - hard coded app name to be delivered to your log server.

  • logServer - in case you want to use log server, just pass the url and it will post to it.

  • Levels - an array with new levels and updated attributes for current levels. New levels must have name and notify/console state, otherwise it won't work.

Example:

var trk = require('trk-log').init({ app: 'test', logServer: 'http://test.com:4000/log', levels: [{name: 'test', notify: false, console:true}, {name: 'notice', notify:true, logServer:'http://log.test.com:4000/log}] });

trk.test('shubi'); //will set test event (new custom event) with "shubi". trk.info('dubi'); //will set info event (console only) with "dubi". trk.notice('zubi'); //will set notice event with "zubi" and then will notify (as you overrided it) about it to "http://log.test.com:4000/log" (again, as you explicitly override it) using post. trk.error('rubi'); //will error event (console) with "rubi" and then will send it to "http://test.com:4000/log" using post.

More:

Default levels are available inside index.js and you can override them, as mentioned above, if you want: var levels = [ {name: 'info', color: 'green', notify: false, console: true}, {name: 'notice', color: 'yellow', notify: false, console: true}, {name: 'error', color: 'red', notify: true, console: true} ]

P.S: If you use multi file app or handling production and development envs, I suggest set external module for the logging settings and init.

This package is on ALPHA mode and I recommend not using it for now.