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

level-onion

v0.0.2

Published

A levelup wrapper interface to add/modify behavior of a levelup instance.

Downloads

12

Readme

level-onion

NPM

Extend a levelup instance in layers, like an onion.

Each layer you add can expose new functionality or modify functionality of inner layers, or you can bypass the layers by using the inner unmodified layers.

WARNING This is currently experimental, and primarily a proof-of-concept. There are no guarantees that this will be a best practice for working with levelup, or be adopted by any significant portion of the levelup ecosystem.

Pros: Simple & low impact.

Cons: I'm not exactly thrilled with the convention it requires wrapping modules to comply with.


Example: case-insensitive keys:

Create a wrapping layer:

  function Upper() {
    // Required
    this.type = "upper"
    // Default false, if true it will prevent you from double-wrapping with this wrapper.
    this.unique = false
  }

  // Requires an install method that takes the wrapped db and the parent it is wrapping
  Upper.prototype.install = function (db, parent) {
    db.put = function (key, value, cb) {
      parent.put(key.toUpperCase(), value, cb)
    }

    db.get = function (key, cb) {
      parent.get(key.toUpperCase(), cb)
    }

    // ... etc.
  }

Wrap a levelup instance with your wrapping layer:

var level = require("level")
var wrap = require("level-onion")

var ldb = level("/tmp/db")
var db = wrap(db, new Upper())
// ldb remains intact and unmodified
// db now has the wrapper installed