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

grpc.server

v3.0.2

Published

a simple abstraction around grpc.Server

Downloads

12

Readme

grpc.server

a simple abstraction around grpc.Server


Build StatusCoverage StatusISC LicenseNodeJS

JavaScript Style Guide

api

const server = require('grpc.server')

  • server(an optional {})
    • address string with the format url:port
    • credentials can use credentials.createInsecure or with certificates through an object { key, server }, passed as a Buffer
    • metadata set metadata that can be used in all calls, an array with { key: value }

methods

  • addServices(an array with the services object)
    • package proto package name
    • name service name
    • proto proto file
    • methods an object with the methods
  • start(callback function)
  • stop(callback function)

note: you can use unary, stream or bidirecional since the comm type should be handled on the proto files and in the methods

example

const server = require('grpc.server')

// proto file
/*
syntax = "proto3";

package helloWorld;

// The greeting service definition.
service Greeter {
  // Sends a greeting
  rpc sayHello (HelloRequest) returns (HelloReply) {}
}

// The request message containing the user's name.
message HelloRequest {
  string name = 1;
}

// The response message containing the greetings
message HelloReply {
  string message = 1;
}
*/

const serverA = server()

const services = [
  {
    proto: protos.helloWorld,
    package: 'helloWorld',
    name: 'Greeter',
    methods: { sayHello: sayHello }
  }
]

serverA.
  .addServices(services)
  .startc(cb)


// to stop the server
serverA.stop(cb)

ISC License (ISC)