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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@softkit/logger

v0.1.4

Published

This library is based on pino logger and provides an opinionated logger for Softkit ecosystem.

Downloads

101

Readme

Logger Library

This library is based on pino logger and provides an opinionated logger for Softkit ecosystem.

By default it logs finish request, with request id and time, and also logs all exceptions with stack trace.

In general it is a pain to fine and setup a proper logger for nestjs application.

We solved most configuration problems that we had with logging in our projects.

Also leverage the use of ClsService to have a proper request id in logs.

Installation

yarn add @softkit/logger

Usage

Default interceptors

  • LoggingInterceptor - it will log all incoming requests

Default configuration


import { setupLoggerModule } from '@softkit/logger';

@Module({
  imports: [
    setupLoggerModule(),
  ]
})
export class YourAppModule {}

Update your root config class


export class RootConfig {
  @Type(() => LoggerConfig)
  @ValidateNested()
  public readonly logger!: LoggerConfig;
}

Update your config files

.env.yaml file

logs:
#  useful for development as well
  colorize: true
#  info should be used for production in most cases, unless you want to debug something
  level: info
#  pretty print usually needed only for development, so must be changed in .env-${env}.yaml files for deployment
  prettyPrint: true