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-zookeeper-client-async

v1.0.0

Published

A promises wrapper over https://github.com/alexguan/node-zookeeper-client

Downloads

35

Readme

node-zookeeper-client-async

A promises wrapper over https://github.com/alexguan/node-zookeeper-client

For the most part it has each method included in the original node-zookeeper-client, with each method with a callback having an additional Async variant (e.g. createAsync).

The symantics are slightly different in that operations on nonexistant nodes typically do not reject (i.e. return an error), but rather resolve null.

Documentation

For more specific information see the documentation

Example

const zk = require('node-zookeeper-client-async');


(async function main() {
    const client = zk.createAsyncClient("127.0.0.1:2181");

    // connect to the server
    await client.connectAsync();
    console.log('connected!');

    // create a node
    const rootPath = await client.mkdirpAsync('/test');
    console.log(`created ${rootPath}`)

    // add some ephemeral nodes
    await client.createAsync('/test/counter-', Buffer.from('first'), null, zk.CreateMode.EPHEMERAL_SEQUENTIAL);
    await client.createAsync('/test/counter-', Buffer.from('second'), null, zk.CreateMode.EPHEMERAL_SEQUENTIAL);

    // list the nodes
    const nodes = await client.getChildrenAsync('/test');

    // print stuff to console
    console.log(`${rootPath} has the children:`)
    await Promise.all(nodes.map(async node => {
        const data = await client.getDataAsync(`/test/${node}`);
        console.log(`  ${node}: ${data.data}`);
    }));

    // delete everything
    await client.rmrfAsync(rootPath);

    // shut down
    await client.closeAsync();
    console.log('disconnected');
})();

Console output:

~/node-zookeeper-client-async$ node example.js
connected!
created /test
/test has the children:
  counter-0000000000: first
  counter-0000000001: second
disconnected