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

ds-node-service

v5.1.0

Published

Base class for Deepstream RPC based Node services

Downloads

67

Readme

ds-node-service

Base module for Deepstream RPC based Node services

Let's start with a comprehensive example:

import { createRpcService } from 'ds-node-service';
import joi from 'joi';

const name = 'service1';
const address = 'localhost:6020';
const credentials = { id: 'serviceId', password: 'secretPassword' };

// The API schema should actually rather be placed in a separate file.
const apiSchema = {
  doSomething: {
    description: 'Description for api-function that does something.',
    args: joi.object().keys({
      name: joi
        .string()
        .trim()
        .alphanum(),
      properties: joi
        .object()
        .unknown()
        .keys({
          birth: joi.date(),
        }),
    }),
    return: joi.number(), // joi-schema for return value or null if no return value
  },
};

// The implementation part would also rather have its own file.
function doSomething({ name, properties }) {
  // DB call or whatever
}
const implementation = {
  doSomething,
};

// Create service, register API (spec & implementation) and start the service.
async function main() {
  const service = createRpcService({
    name,
    address,
    runForever: true,
    credentials,
  });

  service.registerApi(apiSchema, implementation);

  await service.start();
}
if (require.main === module) main();

The base RPC service will on start():

  • Fetch credentials, if a credentialsUrl was provided, and merge the result with the directly specified credentials object.
  • Log in to deepstream with authParams = credentials
  • Provide (rpc.provide(..)) the RPC functions registered with registerApi.
  • Start an idle loop if runForever is true.

The API registration and service start will automatically add a getInterface function that will return an API specification with all methods with argument names & types. Example (from requesting client): client.rpc.make('service1/getInterface').

Some more explanatory comments on the example above:

  • The type assertion system is joi, that needs to be used in the API specification.
  • You can easily fetch Deepstream (for instance as an npm package) and start it locally on its default port 6020, thus localhost:6020 as address.

Change Log

4.0

  • New structure for the api-description object, adding API-description and return value joi-schema in addition to the existing args joi-schema.