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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@omadi/neon

v1.1.15

Published

A logging library for Omadi javascript applications

Readme

Neon

A logging library Omadi javascript application.

Use

import { Logger } from 'neon'

// Set log level.
process.env.LOG_LEVEL = 'warn'

// Initialize.
Logger.initialize({
  project: 'someProject',
  stage: 'someStage',
  requestId: 'requestId'
})

// Will appear:
Logger.error('The system is down.', otherDetails, ...)

// Won't appear - below logging level:
Logger.info('This thing happened you might want to know about.', theThing)

// Show all logs for a certain percentage of subsequent requests, even if below the log level:
process.env.LOG_REQUEST_PERCENT = 10

Logging functions:

Use one of these functions to output a log at the corresponding level. Any number of parameters may be logged. They will be put into the messages property as an array.

  • error (Warn about an unexpected, unrecoverable event. A stack trace is added to the log object.)
  • warn (Warn about an unexpected, but recoverable event.)
  • info (Notify about an expected event.)
  • debug (Always shows when NODE_ENV is dev. Output is not formatted.)
  • system (Keep track of common system-level events. Keep the chatter down here.)

Log Level

Log level is set through the LOG_LEVEL environment variable Options include:

  • none
  • error
  • warn
  • info
  • debug
  • status
  • all

Only logs generated with the function at or above the corresponding log level will be output via console.(error|warn|info|log).

If a requestId is present in a call to initialize, a percentage of requests will display all logs, regardless of log level. This percent is controlled by the LOG_REQUEST_PERCENT environment variable. Defaults to 5%. This behavior is ignored if NODE_ENV is set to dev

Other Functions

initialize

Accepts an object as a parameter. Use this to set context at the beginning of your application for all logs output during that execution. Useful for things like a correlation id or a reference id available in a lambda. It's recommended to include project, stage, and requestId.

setTrace

Allows a stack trace to be set in a different context than where the logs are generated, but more specific than when the logger is initialized. This is useful for getting context outside a promise where the logging is done. Can be called with false to reset to the default behavior.

runOnTest

No logs will be output in a test environment by default. This is determined by checking if the NODE_ENV environment variable is set to test. Call runOnTest with a boolean (default true) to toggle this behavior.

ENV

NODE_ENV

Setting NODE_ENV to dev will not format the output.