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

@lcdev/logger

v0.1.14

Published

Simple structured logger for APIs so that all of our services are consistent

Readme

Launchcode Logger

Licensed under MPL 2.0 npm

A consistent, structured logger for services. This package is a thin wrapper over winston.

The logger that's used and created is literally just winston. We just have a couple utilities here for the common use cases.

Quick Start

yarn add @lcdev/[email protected]
import * as Koa from 'koa';
import {
  getLogger,
  createLogger,
  createLoggerMiddleware,
} from '@lcdev/logger';

// the lifecycle of the logger is simple. create it once, use anywhere with `getLogger`.
createLogger({
  // optional - default to NODE_ENV = 'development'
  debug: true,
  // optional - default to NODE_ENV = 'development'
  outputStackTraces: true,
  // optional - can spawn different loggers with different settings
  name: 'non-default',
  // optional - default true
  stdout: true,
  // optional - insert logs into a file
  logfile: './logs.txt',
});

const createApp = () => {
  const app = new Koa();
  const logger = createLogger();

  // this will log all request/responses on your service
  app.use(createLoggerMiddleware(logger));

  // use the logger anywhere you'd like, specifying the level (again, this is just winston)
  logger.info('created app!');

  return app;
};

Note that you'll need to initialize the global logger before calling getLogger, which will return undefined. If using typescript, getLogger()!.info('hello') is not an antipattern, provided that your program guarantees it's initialization beforehand.

Output

Output will be pretty printed in development (debug) and plain JSON otherwise.

Most important is that we track timestamps, duration, status, and other metadata. It should be easy to parse these later from production logs especially, since it's all raw JSON.