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-http-replicator

v1.1.0

Published

push/pull a dat repo over a HTTP REST API

Downloads

5

Readme

dat-http-replicator

npm install dat-http-replicator

build status

Usage

On a server

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

var server = http.createServer(function (req, res) {
  var progress = replicator.server(datGraphInstance, req, res)
  if (!progress) return

  progress.on('pull', function () {
    console.log('server pulled', progress.pulled)
  })

  progress.on('push', function () {
    console.log('server pushed', progress.pushed)
  })
})

server.listen(9000)

On a client

var replicator = require('dat-http-replicator')
var progress = replicator(datGraphInstance, 'http://localhost:9000')

progress.on('pull', function () {
  console.log('client pulled', progress.pulled)
})

progress.on('push', function () {
  console.log('client pushed', progress.pushed)
})

progress.on('end', function () {
  console.log('done replicating')
})

progress.on('error', function (err) {
  console.log('error!', err)
})

API

progress = replicator.server(datGraph, req, res, [opts], [cb])

Setup a server http handler. Options include:

{
  readonly: true, // do not allow pushes
  writeonly: true // do not allow pulls
}

Note that the progress monitor will be null if this is an endpoint without progress monitoring support.

progress = replicator.client(datGraph, url, [opts], [cb])

Make a replication request. Options include:

{
  mode: 'push' | 'pull' | 'sync' // defaults to sync
}

Progress monitoring

The progress monitor returned will emit push and pull when you send a graph node or receive a graph node. The progress events look like this

{
  transferred: nodesTransferredSoFar,
  length: totalNumberOfNodesToTransfer
}

The latest progress event call also be accessed at progress.pushed and progress.pulled