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

dat-replicator

v3.3.0

Published

Replicate dat using streams

Downloads

20

Readme

dat-replicator

Replicate a dat instance to another one (in a smart way) using nothing but streams

npm install dat-replicator

Usage

Replicating is a simple as piping a few streams

var replicator = require('dat-replicator')
var r1 = replicator(dat1)
var r2 = replicator(dat2)

var send = r1.send()
var rcvd = r2.receive()

send.pipe(rcvd).pipe(send) // will sync dat1 to dat2

Real world example

First setup a dat instance to receive data. Using tcp this could look like

var replicator = require('dat-replicator')
var net = require('net')

var r = replicator(datReceive) // datReceive is a dat instance

net.createServer(function(socket) {
  socket.pipe(r.receive()).pipe(socket)
}).listen(9090)

Then setup another that instance to send the data. Again using tcp

var r = replication(datSend) // datSend is a dat instance
var socket = net.connect(9090)

socket.pipe(r.send()).pipe(socket)

Thats it! All of the changes that datSend have and that datReceive doesn't will be inserted into datReceive.

Metadata

Per default metadata (the change count etc) is exchanged over the stream as well. If for some reason you already have this do

var send = r1.send({meta:{change:100}})
var rcvd = r2.receive({meta:false})

send.pipe(rcvd).pipe(send)

This will disable the metadata exchange

License

MIT