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

cluster-ipc-logger

v1.1.8

Published

This logger is designed to collect logs from cluster workers, child processes even independent node.js processes through IPC (Inter-Process Communication).

Downloads

43

Readme

cluster-ipc-logger

This logger is designed to collect logs from cluster workers, child processes even independent node.js processes through IPC (Inter-Process Communication).

Preview

cluster-ipc-logger

Installation

npm i cluster-ipc-logger

Usage

import { loggerServer, loggerClient } from 'cluster-ipc-logger';
import * as cluster from 'cluster';


if (cluster.isMaster) /* master */ {

    // logger master
    const logger = new loggerServer({
        debug: true,
        directory: './logs',
        saveInterval: 60000 // 1 minute
    });

    // logger for master
    const log = new loggerClient({
        system: 'master',
        cluster: 0
    })

    // log listeners
    logger
        .on('fatal', (msg) => {
            // on fatal logs
        })
        .on('error', (msg) => {
            // on error logs
        })
        .on('all', (msg) => {
            // on all logs
        });

    // detect ^c and save logs before exiting
    process.on('SIGINT', () => {
        logger.save().then(() => {
            process.exit();
        }).catch((err) => {
            throw err;
        });
    });

    // fork workers
    for (let i = 6; i--;) {
        cluster.fork({ workerId: i });
        log.info(`forking worker ${i}`);
    }

    log.debug('debug logs only show up when debug option is set to true');
    log.info('every severity of logs will be save to local storage');
    log.warn('when an error or fatal log occured,');
    log.error('the log content is also saved to another file with prefix [error],');
    log.error('so it is easier to examine the major flaws');


} else /* worker */ {

    // logger for worker
    const log = new loggerClient({
        system: 'worker',
        cluster: process.env.workerId
    });

    log.debug(`worker ${process.env.workerId} standing by`);

}

JSON

//log json
log.info({
    eBooks: [
        {
            language: 'Pascal',
            edition: 'third'
        },
        {
            language: 'Python',
            edition: 'four'
        },
        {
            language: 'SQL',
            edition: 'second'
        }
    ]
});

Note

loggerClient will catch unhandledRejection & uncaughtException and log it as fatal. After sending it to loggerMaster it will automatically kill the client process with process.exit() (as it should be).