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 🙏

© 2025 – Pkg Stats / Ryan Hefner

enter-exit-logger

v1.1.0

Published

typescript/javascript method enter/exit logger based on log4js-node

Downloads

15

Readme

enter-exit-logger

typescript/javascript method enter/exit logger based on log4js-node

enter-exit-logger helps to generate enter/exit traces for typescript methods using the disposable pattern. The trace logs are created with log4js-node.

Installation

Install module:

`npm install enter-exit-logger --save`

Quick Start

With enter-exit-logger method entry/exit logging can easily be added to typescript code. See log4js-node for further information concerning logging configuration.

import { XLog, using } from 'enter-exit-logger';
import { Logger, getLogger, levels, configure } from 'log4js'; 


export class Tester {
    // initialize a logger instance
    private static logger = getLogger('Tester');

    constructor(name: string) {
        using(new XLog(Tester.logger, levels.INFO, 'ctor', 'name = %s', name), (log) => {
            // ...
        });
    }

    private throwException(message: string) {
        using(new XLog(Tester.logger, levels.DEBUG, 'throwException', 'message = %s', message), (log) => {
            throw new Error(message);
        });
    }

    private doTestInternal(val: number): number {
        return using(new XLog(Tester.logger, levels.DEBUG, 'doTestInternal', 'val = %d', val), (log) => {
            log.log('value = %d', val);                 // log with same level as in XLog constructor

            this.throwException("exception tester");    // simulate exception
            return 2 * val;
        });
    }

    public doTest(name: string): number {
        return using(new XLog(Tester.logger, levels.INFO, 'doTest', 'name = %s', name), (log) => {
            try {
                return this.doTestInternal(4711);
            } catch (exc) {
                log.error('Error: ', exc);
            }
        });
    }
}

What effectively is logged is controlled by the logging configuration.

Example (in config/log4js.json):

{
    "appenders": [
        {
            "type": "file",
            "filename": "log4js.log",
            "category": ["Tester", "console"],
            "levels": ["ERROR"],
            "layout": {
                "type": "pattern",
                "pattern": "%d{ISO8601} [%-5p] %-20c %m"
            }
        },
        {
            "type": "console",
            "layout": {
                "type": "pattern",
                "pattern": "%d{ISO8601} [%[%-5p%]] %[%-20c%] %m"
            }
        }
    ],
    "levels": {
        "[all]": "INFO",
        "Tester": "DEBUG"
    },
    "replaceConsole": true
}

The appenders are logging sinks which control where the logs are written. The global levels section controls which level applies to which logger. The logger "[all]" means "all loggers" and defines the default level for all other loggers.