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

@zamatica/logger-configuration

v0.1.1

Published

Configuration parameters and parsing for log levels, prefix, and color toggle. Framework-agnostic core; NestJS-specific helpers behind the /nestjs subpath.

Readme

@zamatica/logger-configuration

Configuration parameters and parsing for log levels, prefix, and color toggle. Built on @zamatica/configuration. Framework-agnostic core; NestJS-specific helpers behind the /nestjs subpath.

Install

bun add @zamatica/logger-configuration
# Optional: install only if you want the NestJS helper
bun add @nestjs/common

Registered configuration parameters

Importing LoggerConfiguration (decorator side-effect) registers three parameters with ConfigurationService:

| Key | Type | Default | Purpose | |------------------------|---------|-------------------------------|----------------------------------------------------| | LOG_LEVELS | string | "fatal,error,warn,info" | Comma-separated list of visible levels. | | LOG_PREFIX | string | falls back to env-var prefix | Prefix string for structured loggers. | | DISABLE_LOG_COLORING | boolean | false | Strip ANSI color codes from console output. |

Canonical levels: fatal, error, warn, info, debug, verbose. Unknown levels in LOG_LEVELS are silently dropped.

Quick example (framework-agnostic)

import { LoggerConfiguration } from '@zamatica/logger-configuration';
import { ConfigurationService } from '@zamatica/configuration';

ConfigurationService.setAppEnvVarPrefix('MYAPP');
ConfigurationService.initialize();

const settings = LoggerConfiguration.parseLogSettings();
// settings.levels          → ['fatal', 'error', 'warn', 'info']
// settings.prefix          → 'myapp'
// settings.disableColoring → false

NestJS subpath

For NestJS apps, map canonical levels to NestJS's LogLevel (note: NestJS uses 'log' for info-level):

import { ConsoleLogger } from '@nestjs/common';
import { mapToNestJsLogLevels } from '@zamatica/logger-configuration/nestjs';

const settings = LoggerConfiguration.parseLogSettings();
const nestLevels = mapToNestJsLogLevels(settings.levels);
const logger = new ConsoleLogger({
  prefix: settings.prefix,
  logLevels: nestLevels,
  colors: !settings.disableColoring,
});

The /nestjs subpath is the only place NestJsLogLevel types appear, so non-NestJS consumers don't pull NestJS-shaped names into their type graph.

Testing the library

Tests that use this library should re-register its parameters after ConfigurationService.__resetForTesting():

import {
  LOGGER_CONFIGURATION_PARAMETERS,
} from '@zamatica/logger-configuration';

beforeEach(() => {
  ConfigurationService.__resetForTesting();
  ConfigurationService.setAppEnvVarPrefix('TESTAPP');
  ConfigurationService.register(
    [...LOGGER_CONFIGURATION_PARAMETERS],
    'LoggerConfiguration',
  );
});