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

connor-base-log

v2.5.0

Published

Base logging library used in a lot of custom projects

Downloads

4

Readme

CircleCI Libraries.io dependency status for GitHub repo GitHub release Dependent repos (via libraries.io)

Connor's Base Log Package

I tend to use this boilerplate package for logging. It automatically sets up Sentry logging and some nice sane defaults for logging with or without a TTY. Designed for use with my default config library.

Install

npm install connor-base-log

How to use

//Assuming you have a config.js boilerplate from my logging lib
//index.js
const config = require('./config'); //This config.js should contain your basic config overwrites like sentry etc.
const log = require('connor-base-log'); 

log.silly("You may as well just print out every tick", {counter: counter});
log.debug("Okay but you still won't be able to read this");
log.verbose("Eh, this is acceptable in production", {customer_bank_account_no: key});
log.info("A descriptive info which will come up as a breadcrumb on Sentry", {with: extraData});
log.warn("Hm, did you mean to do that? This will show up in Sentry as a warning.", {you: screwedup});
log.error("We're going to spam Sentry with this error");
//Protip: You can set the environment variable LOG_LEVEL to change what shows up in your console.

//config.js
const config = require('connor-base-config');
config.load({sentry: {enabled: true, dsn: "https://sentry.makeshift.ninja/"}});
module.exports = config;

Lazy Template

const config = require('connor-base-config');
config.load({sentry: {enabled: true, dsn: "https://sentry.makeshift.ninja/"}});
const log = require('connor-base-log');

Changing defaults

You can change the options by either:

  • Overriding them in config.js
  • Requiring connor-base-config and overwriting with .load in-script
  • Setting environment variables, you can see a full list in the schema