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

@fabcotech/bees

v2.0.5

Published

Javascript library that retreives data from public distributed ledgers, and decides which answer to reject or accept.

Downloads

31

Readme

Bees js

General purpose 0 dependency NodeJS library for reading in distributed ledgers or distributed databases in a trustless manner.

Beesjs has been initiated in the dappy project dappy.tech, to address the problem of unique trustful API endpoints in name systems like the DNS, and more broadly the problem of reading the blockchain state without trusting a node.

npm install beesjs

Use

Beesjs does not know how to query the network, the first argument of resolve is a function that performs the request and returns a string. Each string will then be compared by Bees, until the multi-request either fails or completes.

import { resolver } from 'beesjs';

resolve(
  (id) => {
    return new Promise((resolve, reject) => {
      // this request includes DNS and CA, you are free
      // to query any endpoint any way you want
      https.get(`https://${id}`, (res) => {
        let s = '';
        res.on('data', (d) => {
          s += d.toString('utf8')
        });
        res.on('end', (d) => {
          resolve({
            type: 'SUCCESS',
            data: s,
            id: id,
          });
        });
      }).on('error', (e) => {
        console.log(e);
        resolve({
          type: 'ERROR',
          status: 500,
          id: id,
        });
      });
    });
  },
  /*
    ids
    IDs of the nodes that we want to hit/query
  */
  ['nodea.org', 'nodeb.org'],
  /*
    resolverAccuracy
    The group of [resoverAbsolute] must represent 100% of
    all successful answers
  */
  100,
  /*
    resoverAbsolute
    We want a group of 2 members to represent [resolverAccuracy]% of
    the total of succesful answers
  */
  2,
  a => a
)
  .then(resp => {
    if (resp.statue === "completed") {
      console.log('multi-request / co-resolution succeeded'):

      // resp contains all the groups of answers, you have to iterate over
      // the keys to know which group is the most important
      let winnerGroup = {
        data: '',
        ids: [],
      };
      Object.keys(resp.loadState).forEach((key) => {
        if (resp.loadState[key].ids.length > data.ids.length) {
          winnerGroup = {
            data: resp.loadState[key].data,
            ids: resp.loadState[key].ids,
          };
        }
      });

      console.log(`result of multirequest ${winnerGroup.ids.length} nodes in winning group :`);
      console.log(winnerGroup);
    } else {
      console.log('multi-request / co-resolution did not succeed');
      console.log(resp);
    }
  })
  .catch(err => {
    console.log('something went wrong');
    throw err;
  })

Test and build

# test
npm run test

# build
npm run build && npm run build:declaration