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

@opuscapita/service-client

v1.6.5

Published

Module for http based inter-service-communication for OpusCapitaBusinessNetwork.

Downloads

1,200

Readme

@opucapita/service-client

WARNING: Starting with version 1.0, calls to the methods .get(), .post(), .put(), .patch() and .delete() will resolve and reject the returned promises in a different way that is not compatible to prior versions anymore. In order to be able to rate a server response in an enhanced way, resolved promises get an array passed as input value containing two indexes. The first array index (0) inside represents the result body sent by the remote server. The second index (1) represents a light-weight response object containing status code and headers sent. Rejected promises are getting an Error object as usual containing the original (unparsed) result body inside their message property. And additional property called response provides status code and header sent.


This module provides a simple client class for inter-service communication for OpusCapita Business Network. It is used for easily accessing remote HTTP services and is designed to use Consul in order to dynamically get endpoint configurations to access the target service requested.

To have a look at the full API, please visit the related wiki page.

Minimum setup

First got to your local code directory and run:

npm install @opucapita/service-client

To go with the minimum setup, you need to have access to a running Consul server to get your endpoint configuration. Additionally you need a running web server to use the ServiceClient class.

If all this is set up, go to you code and add the following command:

const ServiceClient = require('@opucapita/service-client');

var client = new ServiceClient({ consul : { host : '{{your-consul-host}}' } });

// main => name of service endpoint in Consul.
// / => path to access on the web server.
client.get('main', '/').spread((result, response) => console.log(result, response));

// example: response contains an error.
client.get('main', '/invalid').catch(e => console.log(e.message, e.response.statusCode));

Result and Response objects

On resolve

When a returned request promise is resolved, two objects are passed as the result. The first contains the actual object returned from the server, the second contains information about the response context. This object is defined like this:

responseObject = {
    statusCode : response.statusCode, // HTTP status code.
    headers : response.headers, // Array of HTTP headers.
    result : resultData, // Instance of the actual result object.
    timeTaken : hrTimerResult // Duration of the service call in milliseconds .
}

On reject

If a returned request promise gets rejected, an Error object is passed to the catch methods available. The passed object gets extended by a response key containing a response object like defined above.

Time taken

The duration of a service call available in the responseObject is measured using the process.hrtime() function and represents the full time in milliseconds a request took including all its preparations and processing.


Origin service based authentication

ServiceClient allows using a service based authentication for service to service calls so an origin service can log-in using its own security credentials. To do calls using service credentials, you have to pass the forceServiceToken parameter to either of the request methods.

For configuration details see the originService key under DefaultConfig.

In order to use the consul configuration here, you have to provide the following keys set up in consul:

  • {{your-service-name}}/service-client/client-username
  • {{your-service-name}}/service-client/client-password
  • {{your-service-name}}/service-client/scope
  • {{your-service-name}}/service-client/client-key
  • {{your-service-name}}/service-client/client-secret

The following keys are optional:

  • {{your-service-name}}/originService/authService/name

Default configuration

The default configuration object provides hints about what the module's standard behavior is like.

{
    mode : process.env.NODE_ENV === 'development' ? ServiceClient.Mode.Dev : ServiceClient.Mode.Productive,
    serializer : JSON.stringify,
    parser : JSON.parse,
    parserContentType : 'application/json',
    serializerContentType : 'application/json',
    alwaysResolveResponses : false,
    timeout : 60000,
    logger : null,
    consul : {
        host : 'consul'
    }
    additionalHeaders : {
        'Content-Type' : 'application/json',
        'X-Service-Type' : 'ocbesbn'
    },
    context : {
        headers : { }
    },
    caching : {
        driver : 'memory',
        defaultExpire : 600
    },
    originService: {
        getConfigFromConsul : true,
        authService : {
            name : 'auth'
        },
        username : null,
        password : null,
        scope : null,
        clientKey : null,
        clientSecret : null,
        scope : 'id, roles',
        tokenKey : 'X-USER-ID-TOKEN'
    }
}