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 🙏

© 2026 – Pkg Stats / Ryan Hefner

files-sync-stream

v0.3.0

Published

Sync files over any transport.

Readme

files-sync-stream

Sync files (or any blobs of data) between two peers, in both directions, over any transport. Originally made for avion.

npm version build status ISC-licensed chat on gitter

  • files-sync-stream is transport-agnostic. You need to pass two channels: one for sending signaling data and one for sending chunks of data.
  • You decide where and how to store the files. files-sync-stream accepts a generic file read function and emits data events when receiving data.

Tings still to be implemented:

  • A basic algorithm to determine the size of the next chunk to be transferred. Should be based on the time to transfer the last chunk.
  • Handling of connection loss, including continuing the sync. This needs a basic have/want logic.

Installing

npm install files-sync-stream

Usage

This assumes the dataTransport and signalingTransport streams are connected the other peer somehow. You would do this for both peers.

const createEndpoint = require('files-sync-stream')

// 1st peer

const leader = createEndpoint(dataTransport, signalingTransport, true)

leader.on('file', (file) => { // handle incoming file
	file.on('start', () => {
		console.log('leader started receiving', file.id)
	})
	file.on('data', (chunk) => {
		console.log('leader received', file.bytesTransferred, chunk.toString('hex'))
	})
	file.on('end', () => {
		console.log('leader finished receiving', file.id)
	})
})
leader.on('done', () => console.log('leader is done'))
// 2nd peer

const follower = endpoint(dataTransport, signalingTransport)
follower.on('file', (file) => {
	// handle incoming file…
})

Use endpoint.add(read, metadata) to transfer a file:

const fromBuffer = require('files-sync-stream/from-buffer')

const data = Buffer.from('aef18a02dd912638', 'hex')
follower.add(fromBuffer(data), {name: 'file.bin'})

Contributing

If you have a question or have difficulties using files-sync-stream, please double-check your code and setup first. If you think you have found a bug or want to propose a feature, refer to the issues page.