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

@meistrari/logger

v2.1.4

Published

@meistrari/logger

Readme

@meistrari/logger


Add environment variables

This library requires 3 environment variables: SERVICE_NAME, SERVICE_VERSION and ENVIRONMENT. Without any of them, it will throw an error and crash the application.

SERVICE_NAME

SERVICE_NAME is a slug-friendly value that represents the name of the service

Use - as word divider. Example: use tela-api instead of tela_api

ENVIRONMENT

ENVIRONMENT should be one of development, staging, forninho or production, any other value will crash the application. Also, this is case sensitive.

When using ENVIRONMENT=development, the logger will output pretty-printed logs to the console.

SERVICE_VERSION

SERVICE_VERSION should change based on the deployed version. This is accomplished with a custom deploy workflow that generates the version for each build. The version is commonly the result of git rev-parse --short HEAD, which returns the short version of the HEAD commit

If your application doesn't have a deploy pipeline yet but you want to instrument it anyway, we recommend using unknown as the value for this variable