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

@myko.pk/logger

v1.2.0

Published

Shared structured logger for MYKOPK packages (Pino wrapper with NestJS-compatible API)

Readme

📑 Table of Contents

📝 Description

@myko.pk/logger provides a structured, Pino-based logger for every MYKO service. It offers a NestJS-compatible API (Logger.log, Logger.error, etc.) so it can be used as a drop-in replacement for @nestjs/common's Logger, while also supporting ad-hoc logging via a global logger instance and request-scoped child loggers. Built-in AuditLogger captures auth, security, and system audit events with structured metadata.

✨ Key Features

  • 🪺 NestJS-Compatible API — Drop-in replacement for @nestjs/common Logger. Use new Logger(MyService.name) as you already do.
  • 📝 Structured JSON Logging — Pino-powered with pretty-print in dev, JSON in production.
  • 🧩 Request-Scoped Child Loggerslogger.child({ requestId }) for distributed tracing.
  • 🔐 Built-in Audit LoggerAuditLogger.logAuth, AuditLogger.logSystem, etc. for structured audit trails.
  • 📘 Fully Typed — Full TypeScript support with typed audit event types and severity levels.

🎯 Use Cases

  • Replacing @nestjs/common Logger across all NestJS microservices with a structured Pino-based logger.
  • Capturing auth events (login success/failure, token refresh) with structured audit metadata.
  • Creating request-scoped loggers with requestId for tracing requests across microservices.
  • Standardising log output format across all MYKO services for centralised log aggregation.

🛠️ Tech Stack

  • 📘 TypeScript
  • 📝 Pino

⚡ Quick Start

npm install @myko.pk/logger
import { Logger } from '@myko.pk/logger';

// NestJS-style logging
class MyService {
  private readonly logger = new Logger(MyService.name);
  doSomething() {
    this.logger.log('Hello world');
    this.logger.error('Something broke', error);
  }
}

// Ad-hoc logging
import { logger } from '@myko.pk/logger';
logger.info('Server started', { port: 3000 });

// Request-scoped child logger
const reqLogger = logger.child({ requestId: 'abc-123' });
reqLogger.log('Handling request');

// Audit events
import { AuditLogger, AuditEventType, AuditSeverity } from '@myko.pk/logger';
await AuditLogger.logAuth(AuditEventType.LOGIN_SUCCESS, AuditSeverity.LOW, {
  mykoId: 'usr_abc',
  ipAddress: '192.168.1.1',
});

Configuration

| Variable | Default | Description | |----------|---------|-------------| | LOG_LEVEL | debug (dev) / info (prod) | Minimum log level | | NODE_ENV | — | Controls pretty-print vs JSON |

🚀 Available Scripts

  • buildnpm run build
  • typechecknpm run typecheck
  • testnpm run test
  • test:watchnpm run test:watch

📁 Project Structure

.
├── CHANGELOG.md
├── CONTRIBUTING.md
├── LICENSE
├── SECURITY.md
├── package.json
├── src
│   ├── AuditLogger.ts
│   ├── Logger.ts
│   ├── PinoLogger.ts
│   ├── index.ts
│   └── types.ts
├── tsconfig.json
└── tsup.config.mjs

🛠️ Development Setup

  1. Install Node.js (v18+ recommended)
  2. Install dependencies: npm install
  3. Build: npm run build

🧪 Testing

This project uses Vitest for testing.

npm run test

👥 Contributors

See the full list of contributors →

👥 Contributing

Contributions are welcome! Here's the standard flow:

  1. Fork the repository
  2. Clone your fork: git clone https://github.com/mykopk/logger.git
  3. Branch: git checkout -b feature/your-feature
  4. Commit: git commit -m 'feat: add some feature'
  5. Push: git push origin feature/your-feature
  6. Open a pull request

Please follow the existing code style and include tests for new behavior where applicable.

📜 License

This project is licensed under the MIT License.

MYKO Pakistan

Detail Information Website myko.pk Email [email protected] About Building digital infrastructure and super-app experiences for millions of users across Pakistan. Built with ❤️ in Pakistan 🇵🇰