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

log4jcore

v4.5.0

Published

logging

Downloads

1,625

Readme

log4jcore

log4jcore

Installation

yarn add log4jcore

Usage

import { logger } from 'log4jcore'

const log = logger('MyClass')

log.info('starting application')

// Multiple arguments are supported, like with console.log.
// One benefit of this approach is that arguments are not
// stringified unless the log level requires the message to be
// logged.
log.info('ip address:', process.env.IP_ADDRESS)

// Use arrow functions to avoid computing a message unless the
// log level requires it to be logged.
log.debug(() => `hostname: ${process.env.HOSTNAME}`)

Configuring Log Levels

Log levels are set to info by default. To change the log level for a logger, pass in an environment variable like DEBUG=MyClass.

Valid environment variable names are:

  • TRACE
  • DEBUG
  • INFO
  • WARN
  • ERROR
  • FATAL

To change the log levels of multiple loggers, use a comma separated list of logger names, like DEBUG=MyClass,AnotherClass.

Changing Appenders

The default appender calls console.log if the message severity is WRAN or lower, and calls console.error if the message severity is ERROR or higher.

setLogFunctionProvider allows you to override this and replace the log writer with a different one. This can be useful if you want to log to a file or log to an external logging API.

You can also pass custom providers to createLogger:

import { createLogger, createDefaultLogProvider } from 'log4jcore'
import fs from 'fs'
import memoryLogProvider from 'log4jcore/memoryLogProvider'
import writableLogFunction from 'log4jcore/writableLogFunction'

const downstream = createLogger({ loggerPath: 'downstream' })
const memLog = memoryLogProvider()
const log = createLogger({
  loggerPath: 'test',
  logProviders: [
    downstream.inputLogProvider,
    memLog,
    createDefaultLogProvider(
      writableLogFunction(fs.createWriteStream('out.log'))
    ),
  ],
})

// later, you can inspect memLog.messages

Logging to a file using log4jcore-file-appender:

log4jcore-file-appender is a simple logging provider that writes to a file instead of stdout / stderr. At the time of this writing, it does not have TypeScript type defs although it does have Flow Type defs.

yarn add log4jcore-file-appender
const { setLogFunctionProvider } = require('log4jcore')
const { createFileAppender } = require('log4jcore-file-appender')

setLogFunctionProvider(createFileAppender({ file: 'messages.log' }))