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

@divvit/logger

v1.0.7

Published

Divvit logging service.

Downloads

6

Readme

Logging service

Small library to abstract logging providers from the code. Features auto-reload of log levels.

Installation

npm install @divvit/logging --save

Usage

var logger = require('@divvit/logger');

the following step is optional

logger.configure(app.get('logging'));

default values will be used and the log config will be shared across the process, so in most cases you can just start logging:

logger.error('One argument');

logger.debug('Several', 'arguments');

logger.info({ object: 'as argument'});

logger.warn(['array', 'as', 'argument']);

// you can mix all of the above

Tests

npm test

Contributing

Nino Ulsamer, Divvit AB

Release History

  • 1.0.0 Initial release
  • 1.0.1 Log error stack trace if available
  • 1.0.2 Bugfix: don't break when logging undefined
  • 1.0.3 Added cleanup method to make sure we send last error event to logentries
  • 1.0.4 Call logentries asynchronously
  • 1.0.5 Bugfix for logentries sending
  • 1.0.6 Don't log to logentries with log level
  • 1.0.7 Send correct log level to logentries