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

nest-crdt

v1.0.0

Published

Nested CRDTs

Downloads

3

Readme

Nested CRDTs

This project allows creation of CRDTs with nesting. For these CRDTs ether custom behavior or provided behavior can be used.

Usage

Use the create function to create a CRDT. This requires an id and a typeName, which will uniquely identify this CRDT over the network. The typeName will also dictate the behavior of this CRDT, and must be a key in the typeStore, which holds all possible behaviors known in the network. Any child of this CRDT, or any other CRDT interacting with this one, must have the same typeStore, messageHandler and cache. The messageHandler is responsible for distributing messages to all CRDTs in this network, and the cache holds every CRDT previously mentioned in the system, for later storage. The cache is expected to be empty at first, when no CRDTs are associated with it yet.

A default typeStore can be imported (called defaultTypes), and extended with custom types, if needed. It is also possible, however, to forgo these default types, and only use custom ones.

import { create, MessageHandler, defaultTypes } from "nest-crdt"

// MessageHandler must be implemented
const messageHandler: MessageHandler = /* see next section */ undefined as any

// Expected to be empty at first
const cache = new Map()

const syncedSet = create('syncedSet', 'g-set', messageHandler, defaultTypes, cache)

// The 'add' method is a modifier specified for 'g-set' in 'defaultTypes',
// and can therefore be used type-safely here.
syncedSet.add("Text to be added to set.").then(() => {
    // The Promise being resolved doesn't imply that the message
    // has been accepted by every node in the network,
    // only that the sending process has been initiated.
    console.log("Added text to 'syncedSet'!")
})

Message Handler

The messageHandler is responsible for ensuring that messages get delivered to CRDTs, even if they haven't yet been accessed locally, and thus don't exist in the cache.

In order to make sure messages get delivered consistently, however, it may instantiate the target CRDT, once a message arrives for it, adding it to the cache, and deliver the message to it.

An implementation of this strategy can be found in the nest-crdt-tools module, in the CachedMessageHandler class.

Building

To build this project first run npm install to install the node libraries, then run npm run build, to invoke the TypeScript compiler.