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 🙏

© 2025 – Pkg Stats / Ryan Hefner

simple-etcd

v0.1.0

Published

An opinionated wrapper around node-etcd.

Downloads

3

Readme

simple-etcd

An opinionated wrapper around node-etcd providing a less powerful but simpler way to read and write values in etcd which also makes use of Q.js to provide a promise rather than callback baed API.

Build Status

Install

$ npm install simple-etcd

Basic usage

var SimpleEtcd = require("simple-etcd");
var simpleEtcd = new SimpleEtcd(); // defaults to localhost:4001
simpleEtcd.set("some-key", { bar: "foo", foo: "bar" }).
.then(function () {
  simpleEtcd.get("some-key", function (value) {
    // value has properies 'bar' and 'foo' with values 'foo' and 'bar'
  });
})

Creating an instance of SimpleEtcd

The SimpleEtcd constructor matches that of node-etcd. With no parameters it defaults to connecting to Etcd via localhost and port 4001.

Setting values

simpleEtcd.set("some-key", { bar: "foo", foo: "bar" });

The set method returns a promise which you can use to wait until the value has been set.

For simple values the behaviour is exactly the same as node-etcd.

So for example the following code will set the key "/foo" to the value "bar".

simpleEtcd.set("foo", "bar");

However if the value being set is an object them SimpleEtcd unwraps each property and creates keys within Etcd which match the structure of the object.

So for example this code,

simpleEtcd.set("foo", { bar: "foo", who: { har: 42 } });

will write the following keys:

"/foo/bar" -> "foo"
"/foo/who/har" -> 42

This behaviour of spreading the properties of an object over multiple keys differs from the default behvaiour of node-etcd.

Getting values

simpleEtcd.get("some-key")

This code returns a promise that will eventually resolve to the value of that key in Etcd. As with the set functionality, for simple values this will behave as node-etcd.

So for example given the key "/some-key" with a value of "foo" the previous code would resolve to "foo".

For keys under which there are child keys present, SimpleEtcd will recursively fetch the child values and construct an object representing all the keys below the specified key.

So given the following keys:

"/some-key/foo" -> "bar"
"/some-key/bar" -> "foo"
"/some-key/hey/ho" -> "let's go!"

Then the following code,

simpleEtcd.get("some-key")

would eventually resolve to the following value:

{
  "foo": "bar",
  "bar": "foo":
  "hey": {
    "ho": "let's go!"
  }
}