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

@gradientedge/logger

v4.0.0

Published

Request-context sensitive logger package

Downloads

48

Readme

@gradientedge/logger

Usage

This package is only intended for use within a node environment.

Using the default logger instance

You don't need to create any objects in order to start logging. It's as simple as:

import log from '@gradientedge/logger'

log.debug('Your message here', { additionalData: 123 })

The log object here is a singleton that's created when the @gradientedge/logger package is first imported.

Creating your own logger instance

If you want more control over the creation of the Logger instance, you can create your own:

import { Logger, LoggerLevel } from '@gradientedge/logger'

const myLogger = new Logger({
  level: LoggerLevel.ERROR,
})

myLogger.error('Major problem!')

Using with @gradientedge/als

The @gradientedge/als is a simple suite of functions that allow you to create AsyncLocalStorage via the create function, and then retrieve that data via the retrieve function.

As you'll see in the index.ts file, we use JavaScript's Proxy class to check to see if we have async local storage data available to us each time any of the Logger methods are called. If we do, then we check for logger property on that data object. If that exists, and is an instance of Logger, then we call the log method on that Logger instance rather than on the singleton instance.

Here's an example:

import { Logger, LoggerLevel } from '@gradientedge/logger'

const myLogger = new Logger({
  level: LoggerLevel.WARN,
  baseData: {
      requestId: '1234'
  }
})

const context = {
  logger: myLogger
}

als.create(context, async () => {
  
  log.debug('Test message', { name: 'Jimmy' })
  
  // Prints the following:
  //
  // {
  //   "level": "debug",
  //   "message": "Test message",
  //   "base": {
  //     "requestId": "1234"
  //   },
  //   "data": {
  //     "name": "Jimmy"
  //   }
  // }
})

Setting the log level with an environment variable

You can define a LOGGER_LEVEL environment variable with one of the following values:

  • debug
  • info
  • warn
  • error

If set, this will be used as the default log level for any new instances of the Logger class.