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

dollidb

v1.0.5

Published

## Overview

Downloads

2

Readme

DolliDB

Overview

DolliDB was inspired by Reddit's Thing DB. In DolliDB there are Items and there is Data. Each Item has Data associated with it. For example, say you want to store a list of Users and their details. There would be a User Item table, which would have an ID and any fields that would be indexable. Items would be arbitray data that is linked to the User item by its ID. Each Item has an ItemID that references the item it belongs to.

Under the hood DolliDB coverts objects to paths. This allows for easy writing and updating of deeply nested, artibtraily named objects.

Here's an example of how DolliDB would convert an object to paths:

  const userData = {
    address: {
      street: '1 Sansome',
      state: 'CA',
      city: 'San Francisco',
    },
    name: 'Chester',
  }

Say we created a User item with the ID as 1. The above object would be converted to the following and each primative field would be saved as its own row in Dynamo with 3 fields, ItemID, Path, and Value:

| ItemID | Path | Value | | ------ | ---- | ----- | | 1 | address.street | 1 Sansome | | 1 | address.state | CA | | 1 | address.city | San Francisco | | 1 | name | Chester |