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 🙏

© 2025 – Pkg Stats / Ryan Hefner

grpcjs-interceptors

v0.1.15

Published

This library provides a way to instrument Node.js gRPC clients and servers with interceptors/middleware. Server-side interceptors are [not yet implemented](https://github.com/grpc/grpc-node/issues/419) in grpc for node. This library is a temporary fix fo

Downloads

92

Readme

grpc-interceptors

This library provides a way to instrument Node.js gRPC clients and servers with interceptors/middleware. Server-side interceptors are not yet implemented in grpc for node. This library is a temporary fix for this. Node module grpc-js is used.

Fork

Original repository here. Only two small changes in file server-proxy.js were done in this fork.

This fork was to allow better password authentication through interceptors. In original library, it was not possible to raise an error if authorization was denied.

In this fork, the interceptor has now access to the callback (of the RPC call). That way, it's now possible to cancel the RPC by calling the callback with an error. This is necessary when doing simple user/password authentication through interceptors.

For much better security, use also TLS mutual authentication.

Install

npm install git+https://github.com/mfecteau34/node-grpc-interceptors.git

Usage

This usage example takes for granted that two RPC metadata parameters are sent with the RPC call. One parameter is "user", and the other "password".

If using the grpcurl utility for testing, add those parameters in the command line : -rpc-header 'user: rpcuser' -rpc-header 'password: abc123'

Lodash is also used to get the parameters easily.

const interceptors = require('grpc-interceptors');
const _ = require('lodash');

const server = interceptors.serverProxy(new grpc.Server());
server.addService(proto.MyPackage.MyService.service, { Method1, Method2 });

// Original version did not have "callback" as a parameter.
const myMiddlewareFunc = async function (ctx, next, callback) {

    // do stuff before call
    console.log('Making gRPC call...');
    
    // Doing authentication
    let user = _.get(ctx,'call.metadata._internal_repr.user[0]','undefined')
    let password = _.get(ctx,'call.metadata._internal_repr.password[0]','undefined')
    if (user == "rpcuser" && password == "abc123") { 
        // Executing the RPC call only if the authentication was successful
        await next();
        // do stuff after call
        console.log(ctx.status.code);
    } else {
        // The whole point for this fork was to have access to callback function ...
        callback(new Error("Unauthorized"));
    }

}

server.use(myMiddlewareFunc);