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

peachplumdb

v1.3.0

Published

This API provides a basic CRUD (Create, Read, Update, Delete) functionality for collections and documents stored in PeachPlumDB.

Readme

PeachPlumDB API

This API provides a basic CRUD (Create, Read, Update, Delete) functionality for collections and documents stored in PeachPlumDB.

Getting Started

Intall Globally

npm i -g peachplumdb

Run the server

Start the server by running peach. The server listens on port 6060

Usage

const collectionId = 'yourCollectionId';
const docId = 'yourDocId';

fetch(`/collections/${collectionId}/${docId}`)
  .then(response => {
    if (!response.ok) {
      throw new Error(`Request failed with status: ${response.status}`);
    }
    return response.json();
  })
  .then(data => {
    console.log('Document data:', data);
    // You can handle the retrieved data here
  })
  .catch(error => {
    console.error('Error:', error);
    // Handle error cases here
  });

Endpoints

The following endpoints are available:

  • GET /collections/:collectionId/:docId: Retrieves a specific document in a collection.
  • GET /collections/:collectionId: Retrieves all documents in a collection.
  • POST /collections/:collectionId/:docId: Creates a new document in a collection.
  • PUT /collections/:collectionId/:docId: Updates a specific document in a collection.
  • DELETE /collections/:collectionId/:docId: Deletes a specific document in a collection.

Request and Response Format

All requests and responses use JSON format.

GET /collections/:collectionId/:docId

  • Parameters:
    • collectionId: the ID of the collection to retrieve the document from
    • docId: the ID of the document to retrieve
  • Response: the JSON data of the retrieved document

GET /collections/:collectionId

  • Parameters:
    • collectionId: the ID of the collection to retrieve all documents from
  • Response: an array of JSON data of all documents in the collection

POST /collections/:collectionId/:docId

  • Parameters:
    • collectionId: the ID of the collection to create a new document in
    • docId: the ID of the new document
  • Request body: the JSON data of the new document
  • Response: status code 201 if the document was created successfully

PUT /collections/:collectionId/:docId

  • Parameters:
    • collectionId: the ID of the collection to update the document in
    • docId: the ID of the document to update
  • Request body: the JSON data to update the document with
  • Response: status code 204 if the document was updated successfully

DELETE /collections/:collectionId/:docId

  • Parameters:
    • collectionId: the ID of the collection to delete the document from
    • docId: the ID of the document to delete
  • Response: status code 204 if the document was deleted successfully