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 🙏

© 2026 – Pkg Stats / Ryan Hefner

console-file-log

v1.0.0

Published

pipe console.log to files

Readme

console-file-log

Save console.log content to a file. Use fancy-log to do console and save the same content to a file.

I use it in a child_process spawn or fork case. When the main process ended, the console of subprocess is unavaliable. Usually we may save the log to a file.

Usage

var filelog = require("console-file-log");

var mylog = filelog({
	append: true,    	//appendFile or writeFile (default: false)
	fname: "mylog.txt",      //name of log file (default: file-log(2-23).txt)
	eol: "\n"		 //eol (default: os.EOL)
});

mylog.log("this is a test log");
// [18:38:04] this is a test log (console)
// [18:38:04] = log =   this is a test log (file)

mylog.warn("this is a test warn log");
// [18:38:04] this is a test warn log (console)
// [18:38:04] = warn=   this is a test warn log (file)

API(same as fancy-log, thanks a lot)

log(msg...)

Logs the message as if you called console.log but prefixes the output with the current time in HH:MM:ss format.

log.error(msg...)

Logs the message as if you called console.error but prefixes the output with the current time in HH:MM:ss format.

log.warn(msg...)

Logs the message as if you called console.warn but prefixes the output with the current time in HH:MM:ss format.

log.info(msg...)

Logs the message as if you called console.info but prefixes the output with the current time in HH:MM:ss format.

log.dir(msg...)

Logs the message as if you called console.dir but prefixes the output with the current time in HH:MM:ss format.