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

personal-backend

v0.1.0

Published

A personal backend for personal projects

Downloads

7

Readme

A simple backend for personal projects

This is a simple Socket.io server for getting, putting, patching JSON-encodable data on a per-user basis.

Allows users to add collaborators which have read/write access to the granter's data. That's right! A personal backend with collaboration! I wrote this initially for a home inventory management app to be shared with my wife; so, kind of personal.

User data has a version number. Clients specify the current version for updates.

Updates may be full replacements or patches/merges.

Clients can fetch or get the full data or just some paths therein (e.g. a.b.c).

Clients can watch for changes to a user's data (including their own) as long as they are the owner of the data or a collaborator thereof.

UserData

{
	"metadata": {
        "username": String,
        "version": Number,
        "collaborators": [Username],
        "createdAt": Date,
        "lastUpdate": { "at": Date, "by": Username }
    },
    "userdata": Object
}

Client Messages

'signup'    
'auth', token    
'update', newData, version, targetUsername=null, patch=false    
'fetch', targetUsername=null, fields=null
'watch', targetUsername
'unwatch', targetUsername

Server Messages

'auth', username, token    
'version', username, version    
'error', message    
'data', targetUsername, data
'change', targetUsername, data

Error Messages

'invalid token'
'version mismatch'
'unauthorized'

Updates

newData = {
  metadata: {
    version: int,             // expected server version of data
    collaborators: [String]   // replaces entirely regardless of patch
  },
  userdata: Object            // replacement or changes (for patch)
}

Fields

fields = [
  'a.b',                      // {a: {b: 1}}
  'c',                        // {c: 'foo'}
  'd.e.f'
]

Fields are a poor man's GraphQL. Specifying some fields to fetch or watch will only return some fields and the data in a data or change message from the server will take the same shape.

Configuration

ENV

PORT=8080
CACHE_SIZE=100
CACHE_MAX_AGE=900000
JWT_SECRET=...
MAX_DATA_SIZE_JSON=65536
DEBUG=api

TODO

  • Rate limit signups from the same IP but this is a cat and mouse game

Author

Brian Hammond [email protected]