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

@brandonxiang/ges

v3.0.0

Published

gRPC experimental server that support koa-like interceptor

Downloads

2

Readme

grpc-experimental-server

gRPC experimental server that supports koa-like interceptors

Usage

npm i ges grpc
import ExperimentalServer from 'ges';

const server = new ExperimentalServer();

server.addService(/* ... */);

// add interceptor
server.use(async (context, next) => {
  // preprocess
  const start = Date.now();
  try {
    await next();
  } finally {
    // postprocess
    const costtime = Date.now() - start;
    console.log('costtime is', costtime);
    console.log('unary response is ', context.response);
  }
});

serer.bind(/* ... */);
server.start();

gRPC has 4 kinds of call:

| handle type | request is stream or not | response is stream or not | | ------------------------- | :----------------------: | :-----------------------: | | handleUnaryCall | ❌ | ❌ | | handleClientStreamingCall | ✅ | ❌ | | handleServerStreamingCall | ❌ | ✅ | | handleBidiStreamingCall | ✅ | ✅ |

Context

  • call current gRPC call
  • definition the method definition of current call
  • response response if response is not stream
  • onFinished(...) you can listen on call finish event, no matter response of current call is stream or not. So you don't need to care about what kind is the call. It is very useful to do something like tracing, logging

Notes

  • await next() would wait the call to be finished if response is not stream.