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

synced-varhash

v1.1.0

Published

An observ-varhash implementation that is created from and kept in sync with a CRDT set

Downloads

843

Readme

synced-varhash

This is a package that keeps a local observ-varhash in sync with a CRDT Set.

NPM

Build Status

Why?

This is useful in the case that you have a front-end application written using mercury (or similar) and you want to keep a varhash in sync between a number of entities. The case that I've used this with is WebRTC and it's pretty awesome :)

Example Usage

var Doc = require('crdt').Doc;
var SyncedHash = require('synced-varhash');
var cuid = require('cuid');

// create two documents
var docs = [new Doc(), new Doc()];

// create the hashes
var hashes = docs.map(SyncedHash());

// create the replication streams
var streams = docs.map(function(doc) {
  return doc.createStream();
});

// replicate between doc:0 and doc:1
streams[0].pipe(streams[1]).pipe(streams[0]);

// watch hash:1 for changes
hashes[1](function(data) {
  console.log('hash:1 changed: ', data);
});

// add some docs to hash:0
setInterval(function() {
  hashes[0].put(cuid(), { tick: Date.now() });
}, 1000);

Known Limitations

While synced-varhash is capable of serializing nested observables (such as observ-struct) over a CRDT, at this stage the deserialized data will be simple JS types on the receiver ends. For this reason, it is recommended that only simple data is serialized at this time.

License(s)

ISC

Copyright (c) 2015, Damon Oehlman [email protected]

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.