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

@vyce/logger

v2.0.1

Published

Logger for Node

Downloads

26

Readme

logger-lib

Custom Vyce NestJS logger

Installation

npm i vyce-slogger

After that add one of the following options to app/main.ts, This will overwrite the default @nestjs/common Logger and you can use the logger from there.

Option 1:

import { VyceLogger } from '@vyce/logger';

const app = await NestFactory.create(AppModule, {
  logger: new VyceLogger(),
});

Option 2:

import { VyceLogger } from '@vyce/logger';

const app = await NestFactory.create(AppModule, {
  bufferLogs: true,
});

app.useLogger(new VyceLogger());

Parameters

The logger service takes only one optional parameter isDev, when this is set to true then the logged output is colored based on the message level and content + the logging level is set to debug (otherwise info). Default value is isDev = process.env.NODE_ENV === "development" so colors should always be enabled in dev. We want colors disabled in production, because cloudwatch does not support colored output and it would just add extra junk there.

const app = await NestFactory.create(AppModule, {
  logger: new VyceLogger({ isDev: true }),
});

Usage

The logger supports all standard Nestjs logging levels log (info), warn, error, debug, verbose and they all act the same way, just change the logging level of the output.

You can pass as many parameters as you want to the logging function and based on the type of the parameter the logger will decide what to do with it. The order of them does not matter at all.

  • All string parameters will be concatenated to build a single log message logger.log("abc", "def") -> "abc def"
  • Error will be populated to a custom error object which will be logged out, all error metadata is logged out there as well
  • All other extra data is populated to a custom meta object which will be log out
import { Logger } from '@nestjs/common';

export class SomeClass {
  private readonly _logger = new Logger(SomeClass.name);

  this._logger.log("Some log message", {some: "meta data"})
  this._logger.log("Some log message", {some: "meta data"}, "second part of message")
  this._logger.error("Some log message", new Error("bla bla"))
  this._logger.error(new Error("bla bla"), "Some log message", {meta: "data"})

}

Example log: