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

tablic-grpc-logger

v1.1.1

Published

A NestJS interceptor for logging gRPC requests.

Readme

gRPC Logger for NestJS

A robust gRPC interceptor for NestJS applications that provides structured and detailed logging. This interceptor captures essential request and response details, including:

  • Method Name: The gRPC method being invoked.
  • Client IP: The originating IP address of the request.
  • Metadata: Any metadata sent along with the request.
  • Request Data: The payload received by the server.
  • Response Time: Time taken to process the request.

Installation

You can install the gRPC logger using npm:

npm i tablic-grpc-logger

Example Log Output

Screenshot 2025-03-08 at 10 26 34 PM

Screenshot 2025-03-08 at 10 26 15 PM

Usage in a NestJS App

To use the gRPC logger in your NestJS application, import the LoggingInterceptor in your controller and apply it using the @UseInterceptors() decorator:

import { Controller, Get, UseInterceptors } from '@nestjs/common';
import { AppService } from './app.service';
import { GrpcMethod } from '@nestjs/microservices';
import { LoggingInterceptor } from 'tablic-grpc-logger';

@UseInterceptors(LoggingInterceptor)
@Controller()
export class AppController {
  constructor(private readonly appService: AppService) {}

  @Get()
  getHello(): string {
    return this.appService.getHello();
  }

  @GrpcMethod('UserService', 'GetUserById')

  getUserById(data: { id: string }) {
    const users = [
      { id: '1', name: 'John Doe', email: '[email protected]' },
      { id: '2', name: 'Jane Doe', email: '[email protected]' },
    ];

    const user = users.find((user) => user.id === data.id);
    if (!user) {
      return { error: 'User not found' };
    }

    return { user };
  }
}

Contribution

We welcome contributions to improve this project! Here are some ways you can contribute:

  • Bug Fixes: If you find a bug, please submit an issue on GitHub and, if possible, provide a fix in a pull request.
  • Feature Requests: Have an idea for a new feature? Open an issue with a description of the feature, and we can discuss it.
  • Code Improvements: Feel free to suggest or submit code improvements for better performance, cleaner code, etc.

Steps to Contribute:

  1. Fork the repository.
  2. Create a new branch for your feature or bug fix.
  3. Make your changes.
  4. Run tests (if applicable) and ensure everything works as expected.
  5. Create a pull request with a detailed description of your changes.

License

This project is licensed under the MIT License.

Issues

If you encounter any issues or have questions, please feel free to open an issue on GitHub. Make sure to include relevant information such as error messages, system environment, and steps to reproduce the issue.