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

js-crdt

v1.0.0

Published

CRDT Conflict-free Replication Data Type

Downloads

41

Readme

js-crdt Build Status

Introduction

CRDT Conflict-free Replication Data Type in JavaScript.

Development

npm install
npm run build
npm test
npm run lint
npm run dist

How crdt/Text type with order/discrete should work? (WIP)

Consider two actors a and b working concurrently on some document. Actor a and b have same origin of the document origin:0. For simplification, origin is not shown here.

a:0
b:0

First actor started working on version a:0, and did some changes xxx. Actor b did not start working on document.

a:0  xxx
b:0

Actor a decided to send his version a:1 to actor b, but before that, he want to be sure that regardless if b receives his changes, he can continue on working his version of document. so he created a snapshot a:1 of his version of document and send changes to actor b.

a:0  xxx  a:1
b:0

Actor b sees incoming changes a:0 of the actor a, so he merge them with his current state and create new version it b:1 a:0

a:0  xxx  a:1
            |
b:0      b:1 a:0

Actor b decides to add something to document yyy, and send his changes to actor a. Actor b in the same manner, before sending his changes to actor a he creates snapshot of his version of document b:2 a:0 and send changes b:1 a:0 to a.

a:0  xxx  a:1
            |
b:0      b:1 a:0  yyy  b:2 a:0

When actor a sees incoming changes, he merge them with his document.

a:0  xxx  a:1          a:2 b:1
            |             |
b:0      b:1 a:0  yyy  b:2 a:0