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

digger-server

v2.0.0

Published

LevelDB backed digger warehouse

Downloads

4

Readme

digger-server

Build status

Warehouse routing for digger-client requests.

install

$ npm install digger-server

usage

Make a digger-level supplier and mount it.

var level = require('level');
var diggerserver = require('digger-server')
var diggerlevel = require('digger-level')

// create a new leveldb - this can also be a sub-level
var leveldb = level('/tmp/digger')

// create a level digger supplier
var supplier = diggerlevel(leveldb)

// create a digger server to mount our level supplier
var digger = diggerserver()

// mount the level supplier onto the server
digger.warehouse(supplier)

// access control
digger.access(function(path, user, mode, next){
	next()	
})

// create a HTTP server to host it
var server = http.createServer(digger.handler())

server.listen(80)

notes

The digger server accepts HTTP requests that have been converted to JSON objects.

A digger req is a read-stream in object mode with the following properties:

{
	method:'get',
	headers:{
		'x-digger-selector':'folder.red'
	},
	url:'/apples'
}

raw requests

You can convert raw HTTP requests using digger-http.

endpoints

Here are the notable endpoints:

  • POST /digger/ship - callback based contracts
  • POST /digger/stream - stream based contracts
  • POST /digger/select - selector resolving
    • /* - warehouse

The first 3 are used for contract resolving - a contract is a complicated multi-step selector / append / save / delete request.

ship

The ship endpoint accepts a contract as its POST data and expects the body of each contract to be present.

stream

The stream endpoint accepts a contract in its x-digger-contract header and will stream the requests input to that contract.

select

This creates selector streams for each of the selector stages and pipes them accordingly.

The input is not JSON packets but context paths.

warehouse

This is the REST controller back to the storage engine - you can call standard HTTP on this (for example to load a single container just GET its url)

licence

MIT