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

easy-grpc-server

v0.3.1

Published

Easy gRPC server. Quick way to implement or mock GRPC services.

Downloads

2

Readme

easy-grpc-server

This is a quick and easy way to bootstrap and/or mock gRPC service with NodeJs having only services definitions, given as a set of protobuf files.

Installation

You can install easy-grpc-server via a package manager:

$ npm install easy-grpc-server --save

Usage

Proto files

Before start initializing server you have to define one or more import directories where roots of protobuf files tree resides.

Your protobuf sources may contain imports of the messages defined in the other protobuf files.

There is no need to define an import directory for the Google Proto API files. They will be imported automatically.

Quick start

The basic example of how to start gRPC server. No service method handlers were defined here. Every call will return Unimplemented gRPC error.

const {GRPCServer, GRPCError} = require('easy-grpc-server');

( async () => {
  const server = new GRPCServer({
          protoPaths: [
              'xcorp/protobuf/parking/parking_service.proto'
          ],
          includeDirs: [
              '/Users/myuser/work/xcorp/parking-proto/src/main/proto'
          ],
          services: [
              'xcorp.protobuf.parking.ParkingService'
          ],
          port: 50051,
          secure: false,
          logger: console
  });
  try {
      await server.start();
  } catch (err) {
      // eslint-disable-next-line no-console
      console.error(err);
      process.exit(1);
  }
})();

GRPCServer API (in pseudo TS types notation)

constructor(settings: ServerSettings)

Constructs GRPCServer instance.

Server settings

In order to properly init server you have to work out first the correct set of the server settings. Server settings supplied to server constructor as follows:

/**
* Server settings
*
* @typedef {Object} ServerSettings
* @property {string[]} protoPaths
* @property {string[]} includeDirs
* @property {string[]} services
* @property {number} port
* @property {boolean} secure
* @property {Object} logger
*/
  • includeDirs is a list of directories where your proto files packages tree resides
  • protoPaths is a list of proto files which contains service definitions you want to implement. You have to supply relative path to one of the directories defined in the includeDirs
  • services is a list of service definitions you want the server to implement. Full name including packages must be specified. For example xcorp.protobuf.parking.ParkingService
  • port is port number server will be bound to
  • secure is a boolean flag specifying if we want to run secured communication or opentext http/2.0 calls. Currently, the only an insecure option is supported.

start(): Promise<number>

An async function that starts the server and returns port server was bound to.

addHandler(service: string, method: string, handler: (call: object, callback: Function) => void)

This method assigns handled to the given service object (for example xcorp.protobuf.parking.ParkingService) and chosen method (for example addCar). The handler must be a function that accepts two parameters

  • call - gRPC call context
  • callback - classic JS callback (error, result) function. Error supplie to callback must be of GRPCError type
      
    const {GRPCServer, GRPCError, status} = require('easy-grpc-server');
      
    const err = new GRPCError(status.INVALID_ARGUMENT, 'Car plate number is invalid', carPlate)
    For good explanation how to write handlers and use callbacks please check the article gRPC Basics - Node.js.

Mocking

Initially, this project was made for quick mocking of the third party gRPC services for the local development. Some mock related helper functions will be added to the project over time. At the moment there is one helper Handler Factory - Matching Handler Factory

Matching Handler

The idea behind Matching Handler that you define a list of matching patterns for the request and the typical response for the corresponded pattern. The matching pattern has a structure {match: object, reply: object}.

    const easyGRPC = require('easy-grpc-server');
    const matchingHandlerFactory = easyGRPC.handlers.matchingHandler;
    
    server.addHandler(
            'xcorp.protobuf.parking.ParkingService',
            'CurrentBilling',
            matcherFactory(
                [
                    {
                        match: {
                            plate: 'ABC1234'
                        },
                        reply: {
                            plate: 'ABC1234',
                            billing: {
                                startTime: 1564981295210,
                                plan: 'WORKDAY',
                                billedTime: 360000,
                                sum: 200,
                                vat: 36
                            }
                        }
                    }
                ]
            )
        );