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

@zaneray/gcp-node-logging

v1.1.1

Published

Seller of the Product

Readme

ZaneRay Node Logging

  • A wrapper around Winston
  • Supports logging to Google StackDriver for deployed applications
  • Provides logger 'Singleton' for convenience
  • Provides configurable logging 'Singleton', to provide custom-configured loggers

Definitions

Environments

  • development
  • test
  • staging
  • production

Transports (transports.js)

  • defines where to log in each Environment
  • development->Console
  • test->Google Stackdriver
  • staging->Google Stackdriver
  • production->Google Stackdriver

Options (options.js)

  • defines how to log in each Environment
  • development->Timstamp Level Message
  • test->JSON
  • staging->JSON
  • production->JSON

Log Levels - from Winston

  • 0: error
  • 1: warn
  • 2: info
  • 3: verbose
  • 4: debug
  • 5: silly

Usage (see test/loggingTest.js)

in your node project

npm install --save @zaneray/gcp-node-logging

in your application code

const {logger} = require("@zaneray/gcp-node-logging");
// Writes some log entries
logger.info("here's some information");
logger.warn("something might be wrong");
logger.error("something is wrong, seriously");

//change log level to log warn and above
logging.setLevel("warn");
//show the current level
logger.warn(logging.getLevel());

// Writes some log entries
logger.info("here's some information");
logger.warn("something might be wrong");
logger.error("something is wrong, seriously");

to configure different transports, or formats, the 'logging' object is also esposed.

const logging = require("@zaneray/nodejs-logging");
let transports = [new winston.transports.Console({level: "silly",handleExceptions: true})];
let format = format.json();

// set process.env.NODE_ENV in the runtime
// logger level and output method is determined by environment (see transports.js and options.js)
const logger = logging.createWithTransportsAndFormat(transports,format);

// Writes some log entries
logger.info("here's some information");
logger.warn("something might be wrong");
logger.error("something is wrong, seriously");