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

nsp-log

v3.0.2

Published

a logger that targets rabbitmq that we use for nsp stuff

Downloads

3

Readme

nsp-log

This is the logger we use for backend stuff for the node security platform. It sends stuff to stackdriver logging.

Usage:

const Logger = require('nsp-log');
const logger = new Logger({
  name: 'module_name',
  disable: false, // if set to true all the logging methods will be silently ignored
  auth: {}, // stackdriver auth options
  project_id: 'my-cool-project', // google cloud project
  resource: { /* stackdriver resource */ } // OPTIONAL
});

logger.log('hi', { some: 'labels' });
logger.info();
logger.debug();
logger.warn();
logger.error();

If auth is defined it will be used to authenticate the logging agent, this is usually not needed when deployed in GCE and can be left out entirely.

If resource is not defined, but project_id is or GCLOUD_PROJECT is exported in your environment, a resource will be automatically created for you. If resource, project_id and GCLOUD_PROJECT are all unset this library will fallback to a console based logger.