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

console-files

v2.3.1

Published

Simple package to handle console output to files

Downloads

19

Readme

console-files

Simple Node.js package to write application outputs to files.

It works as a default JavaScript Console object, but with special handlers for .log and .error methods, saving output to configured files.

It also treats application fatal errors (uncaughtException), appending error message to file before exiting process.

Using

npm i --save console-files
const logger = require('console-files')

/*
Do the stuff
*/

logger.log('Hello console-files!')

/*
More work to do
*/

logger.error(new Error('Keep calm, it is just a test ;)'))

Configuration

It's configurable through the following environment variables:

Environment variable | Method | Default --- | --- | --- LOGGER_OUTPUT | .log | ./logger.out LOGGER_ERRORS | .error | ./logger.err LOGGER_FATAL_ERRORS | - | ./_stderr LOGGER_SKIP_FATAL | - | -

Development and production

console-files checks the NODE_ENV to work differently for production and development modes:

const devMode = process.env.NODE_ENV !== 'production'
  • On dev mode it'll output to default console, unless the LOGGER_OUTPUT or LOGGER_FATAL_ERRORS env variable is explicitly set;

  • On production mode it'll output only to files;