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

multidrive

v5.2.1

Published

Manage multiple hyperdrive instances

Downloads

13

Readme

deprecated

More info on active projects and modules at dat-ecosystem.org


multidrive stability

npm version build status Test coverage downloads js-standard-style

Manage multiple hyperdrive archives located anywhere on the filesystem.

Usage

var hyperdrive = require('hyperdrive')
var multidrive = require('multidrive')
var toilet = require('toiletdb')

var store = toilet('./data.json')
multidrive(store, createArchive, closeArchive, function (err, drive) {
  if (err) throw err

  var data = { key: '<64-bit-hex>' }
  drive.create(data, function (err, archive) {
    if (err) throw err

    var archives = drive.list()
    console.log(archives)

    drive.close(archive.key, function (err) {
      if (err) throw err
      console.log('archive deleted')
    })
  })
})

function createArchive (data, done) {
  var db = level('/tmp/' + 'multidrive-' + data.key)
  var drive = hyperdrive(db)
  var archive = drive.createArchive(data.key)
  done(null, archive)
}

function closeArchive (archive, done) {
  archive.close()
  done()
}

Error handling

If there is an error initializing a drive, instead of the whole process failing, an error object with attached .data property will be pushed into the list of archives instead. That means when consuming multidrive.list(), you should check for errors:

var archives = multidrive.list()
archives.forEach(function (archive) {
  if (archive instanceof Error) {
    var err = archive
    console.log('failed to initialize archive with %j: %s', err.data, err.message)
  }
})

This way you can decide for yourself whether an individual initialization failure should cause the whole process to fail or not.

API

multidrive(store, createArchive, closeArchive, callback(err, drive))

Create a new multidrive instance. db should be a valid toiletdb instance. createArchive is the function used to create new Hyperdrive archives. callback is called after initialization. closeArchive is called when drive.remove() is called.

createArchive has an api of createArchive(data, done) where data is passed in by drive.create() and done(err, archive) expects a valid archive.

closeArchive has an api of closeArchive(archive, done) where archive was created by createArchive and done(err) is expected to be called when the archive has been properly closed. closeArchive is called when a specific archive is closed through .close or when through .disconnect all archives get disconnected.

archives = drive.list()

List all archives in the multidrive.

drive.create(data, callback(err, drive[, duplicate]))

Create a new Hyperdrive archive. data is passed into createArchive. If an archive with the same key already exists, returns that instead and sets duplicate to true.

drive.close(key, callback(err))

Remove an archive by its public key. Calls closeArchive()

drive.disconnect(callback(err))

Disconnects the drive from the store and closes all archives (without removing them).

Installation

$ npm install multidrive

See Also

  • https://github.com/karissa/hyperdiscovery
  • https://github.com/mafintosh/hyperdrive
  • https://github.com/Level/level
  • https://github.com/maxogden/toiletdb

License

MIT