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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@graffiti-garden/implementation-local

v0.6.4

Published

A local implementation of the Graffiti API using PouchDB

Readme

Graffiti Local Implementation

This is a local implementation of the Graffiti API using PouchDB. By default, it automatically persist data in both the browser and Node.js using whatever stoage is available in each environment. It can also be configured to use an external CouchDB instance, but using a remote database is insecure.

Installation

In node.js, simply install the package with npm:

npm install @graffiti-garden/implementation-local

In the browser, you can use a CDN like jsDelivr. Add an import map the the <head> of your HTML file:

<head>
    <script type="importmap">
        {
            "imports": {
                "@graffiti-garden/implementation-local": "https://cdn.jsdelivr.net/npm/@graffiti-garden/implementation-local/dist/browser/index.js"
            }
        }
    </script>
</head>

In either case, you can then import the package like so:

import { GraffitiLocal } from "@graffiti-garden/implementation-local";
const graffiti = new GraffitiLocal()

Usage

This is an implementation of the Graffiti API, so to use it please refer to the Graffiti API documentation.

The only major difference is that options can be passed to the constructor to configure the PouchDB instance. The PouchDB instance will create a local database by default, in either the browser or Node.js. However, you could configure it to use an external CouchDB instance as follows:

import { GraffitiLocal } from "@graffiti-garden/implementation-local";
const graffiti = new GraffitiLocal({
  pouchDBOptions: {
    name: "http://admin:password@localhost:5984/graffiti",
  }
})

See the PouchDB documentation for more options.

Extending

Pieces of this implementation can be pulled out to use in other implementations.

// The basic database interface based on PouchDB
import { GraffitiLocalDatabase } from "@graffiti-garden/implementation-local/database";
// The log in and out methods and events - insecure but useful for testing
import { GraffitiLocalSessionManager } from "@graffiti-garden/implementation-local/session-manager";
// Various utilities for implementing the Graffiti API
import * as GraffitiUtilities from "@graffiti-garden/implementation-local/utilities";

TODO

  • Permanently delete content after it has been deleted for a certain amount of time
  • Obscure cursors and make them only usable once.
    • They should expire, too, if they have been around longer than the delete timer.
  • Fix the LAST_MODIFIED_BUFFER hack.