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

node-ledger-client

v1.1.14

Published

Hyperledger client based on Hyperledger fabric SDK for Node.js

Downloads

55

Readme

node-ledger-client

Hyperledger client based on Hyperledger fabric sdk node now supports version 1.3 of Hyperledger Fabric.

Usage

Import in your Typescript file:

import { LedgerClient } from 'node-ledger-client';

Now you can view a 3 functions to working with chaincode:

  1. async doInvoke(fcn: string, args: string[])
  2. async doQuery(fcn: string, args: string[])
  3. async registerChaincodeEvent(chaincodeId: string, peerName: string, eventName: string, onEvent, onError)

async doInvoke

The Invoke method is invoked whenever the state of the blockchain is queried or modified. <br

This method needs two arguments, the first is the name of the function we want to invoke in the chaincode. The second is the array of args that we want to pass to the chaincode function. doInvoke returns a Promise. Example const payload = await ledgerClient.doInvoke(fcn , args);

async doQuery

A chaincode query is somewhat simpler to implement as it involves the entire network, but simply requires communication from client to peer.

It is the same seen just before. Example const payload = await ledgerClient.doQuery(fcn , args);

async registerChaincodeEvent

const config = require('./config-fabric-network.json');
const ledgerClient = await LedgerClient.init(config); 
const invoke = ledgerClient.doInvoke('storeProcessStepRouting', ['test']);

const peerName = config.organizations[0].peers[0].name;
const ccid = config.chaincode.name;
const eventId = "EVENT"; //eventName
let handler = null;
async function main() {
    async function chaincodeEventSubscribe(eventId: string, peerName: string) {
        return ledgerClient.registerChaincodeEvent(ccid, peerName, eventId, (event) => {
            console.log('Event arrived with name: ' + event.event_name + ' and with payload ' + Buffer.from(event.payload));
        }, (err) => {
            console.log('Errore ricevuto nell evento' + err);
            setTimeout(() => {
                chaincodeEventSubscribe(eventId, peerName).then((handler) => {
                    console.log('Handler received ' + JSON.stringify(handler));
                }, (err) => {
                    console.error('Handler received ' + err);
                });
            }, 1000);
        });
    }
    chaincodeEventSubscribe(eventId, peerName).then((handle) => {
        console.log('Handler received ' + JSON.stringify(handle));
        handler = handle;
    }, (err) => {
        console.error('Handler received ' + err);
    });
}
main();

Watch out!!! The string eventName must be the same as the event created in the chaincode!!!