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

architect-log4js

v4.2.1

Published

Architect plugin to provide logging facilities.

Downloads

954

Readme

architect-log4js

Expose log4js as architect service.

Installation

npm install --save architect-log4js

Config Format

{
  "packagePath": "architect-log4js",
  "config": {
    appenders: {
      out: { type: 'console' }
    },
    categories: {
      default: { appenders: [ 'out' ], level: 'info' }
    }
  }
}

}

Usage

Boot Architect :

var path = require('path');
var architect = require("architect");

var configPath = path.join(__dirname, "config.js");
var config = architect.loadConfig(configPath);

architect.createApp(config, function (err, app) {
    if (err) {
        throw err;
    }
    //app.services.log is avaliable now
    var log = app.services.log.getLogger('app');
    log.info('application started');
});

Configure Log4js Architect service with config.js :

module.exports = [{
    packagePath: "architect-log4js",
    config: {
      appenders: [
        { type: "console" }
      ],
      replaceConsole: true
    }
}, './routes'];

config object is passed to log4js.configure method. See log4js configuration for more options.

Consume log service in your application :

{
  "name": "routes",
  "version": "0.0.1",
  "main": "index.js",
  "private": true,

  "plugin": {
    "consumes": ["log"]
  }
}

Eventually use the log service in your app :

module.exports = function setup(options, imports, register) {
    var logger = imports.log.getLogger(); //get default logger
    log.info('plugin initialized.');
    register();
};

request logger

This module provides a log request feature that is not available in log4js itself.

Example :

    rest.get('/', function(req, res) {
        var logger = imports.log.requestLogger(req).getLogger(); //get default logger
        log.info('plugin initialized.');
    });

This will produce :

[2015-02-06 16:03:54.329] [INFO] - [/] plugin initialized.

#### options

  • request.property : request property to log defaults to 'url'. May also be a function that takes a request as first argument.
  • request.format : {string} message format defaults to '[%s] %s', where first placeholder is the request property and the second is the actual message.