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

winston-log-and-exit

v1.0.6

Published

Patch for assuring that winston log messages are written to file before exiting

Downloads

7,675

Readme

The Problem

Winston creates may execute logging callbacks before file streams have been flushed, and creates file streams asynchronously but executes the close methods synchronously, and as a result, the following messages may note be logged to file:

logger.info("This message may not be saved to file.",
    function(){process.exit()})

and:

logger.info("This message probably won't be saved to file.")
logger.close()
process.exit()

The solution

winston-log-and-exit is a patch which adds a log_and_exit() (or equivalently logAndExit()) method to Winston, which can be used with Winston's default logger like so:

var winston = require('winston');
require('winston-log-and-exit');

// add a file transport to winston's default logger
winston.add(winston.transports.File, { filename: 'somefile.log' });

winston.log_and_exit(/* log level */ "info" ,
                     /* log text  */ "This message *will* be included in the log files." ,
                     /* exit code */ 0 )

winston.info("This message *might* be included in the log files.")
process.nextTick(winston.info("This message probably won't be included in the log files.")
setTimeout(winston.info("This message almost certianly won't be included in the log files."),100)

and with a user-instantiated logger like so:

var winston = require('winston');
require('winston-log-and-exit');

var logger = new (winston.Logger)({
    transports: [
        new (winston.transports.Console)(),
        new (winston.transports.File)({ filename: 'somefile.log' })
    ]
});

logger.log_and_exit("info","This message *will* be included in the log files.",0)
logger.info("This message *might* be included in the log files.")
process.nextTick(logger.info("This message probably won't be included in the log files.")
setTimeout(logger.info("This message almost certianly won't be included in the log files."),100)

This can also be used to ensure that uncaught exceptions are logged:

require('winston-log-and-exit');
process.on('uncaughtException', function (err) {
    // use `winston` or your own Logger instance as appropriate
    winston.error("Uncaught Exception",err);
    winston.log_and_exit("info","bye",1);
});

Note that the third argument may optionally be a callback which is responsible for calling process.exit() (and if it doesn't, your begging for a memory leak).

winston.log_and_exit("info","bye",function(){
    try{
        DB.close();
        winston.log("This message will NOT get saved to file!")
    }finally{
        process.exit(0);
    }
});