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

safe-redis-schema

v1.1.0

Published

Type-safe and validated data schemas for Redis and Typescript

Downloads

70

Readme

Safe Redis Schemas

Type-safe and validated data schemas for Redis and Typescript

See ./src/index.test.ts for full example usage of all data types.

You can define a redis data schema, exporting particular definitions:

import { RedisStore, defineObj, defineCounter, defineHashOf, defineHashOfCounters } from 'safe-redis-schema';
import * as Safe from 'safe-portals';

const redisUrl = process.env["REDIS_URL"] || 'redis://127.0.0.1:6379';
const store = new RedisStore(redisUrl);

/**
 * You can access redis directly using store.getRawConnection,
 * or use the Promise-wrapped API of RedisStore itself.
 *
 * However, the real purpose of this library is to define a safe, validated
 * schema for your redis data model.
 *
 * Here we define an example schema.
 */

/* Using a namespace prefix can make redis key naming more hygenic.
 * This mechanism prohibits re-use of keys for different data types.
 */

const ns = store.namespacedBy('myExample:');

export const pageHitCount = defineHashOfCounters(ns, 'pageHits');
/*
 * Prohibited key reuse means that the following would all throw errors,
 * because the key has already been used in a schema definition:
 *
 * defineObj(ns, 'pageHits', Safe.str);
 * defineObj(store, 'myExample:pageHits', Safe.str);
 */

export const people = defineHashOf(
  ns,
  'people',
  Safe.obj({
    name: Safe.str,
    age: Safe.int
  })
);

Then your data schema can be used elsewhere by:

import { pageHitCount, people } from './my_redis_schema';

async function foo() {
    let count = await pageHitCount.incrby('/some/page/url', 1);
    console.log(`count is now ${count}`);

    count = await pageHitCount.get('/some/page/url');
    console.log(`count is still ${count}`);

    await pageHitCount.zero('/some/page/url');

    await people.hset('123', { name: 'Jane', age: 34 });
    console.debug(await people.hget('123'));
}

The types are all built- and run-time validated, so you can't insert the wrong thing into the people schema, retrieve unexpected types from people, or get anything other than a number out of a counter.