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

node-filelog

v1.0.15

Published

Easily log your data to files, with this module.

Downloads

5

Readme

log your data to files

This module gives you the ability to log to files, it uses two logging methods: msg() and err(). As expected msg() is for normal logging, you should use err() to log critical system errors. The logger makes a filename with the current date, this way it separates a different log file for each day. Each file row starts with a timestamp when the log occurred, followed by the keyword in brackets. All this makes it extremely easy for filtering the files with tools like grep.

Simple Usage:

var logger = require('node-filelog'),
    log = new logger();

log.msg('test', 'this is a test log message'); // <163751[test]> this is a test log message

log.err('database', 'authentication error');   // <163751[database]> authentication error

By default the module uses the location of the file that is run from to log your data, for both log and err files. You can custom add your own folders to log just by adding two parameters when instantiating the logger object. ( Folders must exist! )

log = new logger('/path/to/msg-folder', '/path/to/err-folder');

The first parameter is the so called 'keyword', helpful for tagging different logs. If you just want the plain log with no keywords only time and log data use.

log.useShortLog();
 
log.msg('this is a test log message'); // <164924> this is a test log message
log.err('authentication error');       // <164924> authentication error

The format of the date and time is not really readable, but once you understand it it makes sense. Nonetheless there is a possibility to add separators, to make it more human readable:

log.setTimeSeparator(':');

log.msg('test', 'this is a test log message'); // <16:58:31[test]> this is a test log message
log.err('database', 'authentication error');   // <16:58:31[database]> authentication error

The same is applicable for the filename using: log.setDateSeparator(separator)