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

logjet

v0.0.3

Published

Structured, async TypeScript logger with console, file, HTTP transports and NestJS support

Readme

logjet

⚠️ WARNING: This package is experimental and not yet production-ready. Use at your own risk. Breaking changes may occur at any time.

🚀 A powerful, framework-agnostic structured logger with JSON output, multi-transport support (console, file, HTTP), async logging, Bull-based retry queue, and optional NestJS integration.


✨ Features

  • Structured JSON logs – ideal for observability and log aggregation
  • 📦 Multi-transport – supports console, file, and HTTP transports
  • 🔁 Retry mechanism – async HTTP logs are queued via Bull if delivery fails
  • ⚙️ Log levelsinfo, warn, error, debug
  • 💡 Pluggable architecture – easily extend with custom transports
  • 🧱 NestJS wrapper module – optional LoggerModule for drop-in integration

📦 Installation

# install core logger
npm install logjet

# if using NestJS
npm install @nestjs/common

🛠️ Usage Basic Setup


import { Logger } from 'logjet';

const logger = new Logger({
  level: 'info',
  transports: [
    'console',
    'file',
    {
      type: 'http',
      url: 'https://your-log-server.com/logs',
      bull: {
        redisUrl: 'redis://localhost:6379',
        queueName: 'logjet-queue'
      }
    }
  ]
});

logger.info('Server started', { port: 3000 });
logger.error('Something failed', { error: err });

⚙️ Configuration

| Option | Type | Description | | --------------------- | ---------------------- | ------------------------------------------------------------------ | | level | string | Minimum log level (debug, info, warn, error) | | transports | string[] \| object[] | List of transports (console, file, or { type: 'http', ... }) | | filePath | string | Path for file logs (only if file transport is used) | | http.url | string | Target endpoint for HTTP logging | | http.bull.redisUrl | string | Redis URL for Bull queue | | http.bull.queueName | string | Queue name for Bull retry logic |

🚀 NestJS Integration (Optional)


// app.module.ts
import { LoggerModule } from 'logjet/nest';

@Module({
  imports: [
    LoggerModule.forRoot({
      level: 'debug',
      transports: ['console', 'file']
    })
  ],
  providers: [AppService],
})
export class AppModule {}

Inject it anywhere using:


import { InjectLogger, LogjetLoggerService } from 'logjet/nest';

@Injectable()
export class SomeService {
  constructor(
    @InjectLogger() private readonly logger: LogjetLoggerService
  ) {}

  someMethod() {
    this.logger.warn('This is from NestJS logger');
  }
}

🧠 Tip If using NestJS, ensure @nestjs/common is installed in your host project. logjet declares it as a peer dependency.