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

@rlay/schema-registry

v1.0.4

Published

Remote registry client for your rlay schema via redis

Downloads

6

Readme

rlay-schema-registry

Client for registering any rlay schema via redis remotely to improve portability of rlay applications.

Usage

Examples focus on usage with rlay-client-lib which is the most common setup.

We assume

const rlayClient = require('./generated/rlay-client');
const { Client } = require('@rlay/rlay-client-lib');
const Redis = require('ioredis');
const { RlaySchemaRegistry } = require('@rlay/schema-registry');

const rlaySchemaRegistry = new RlaySchemaRegistry({
  db: new Redis(), // connect to redis where registered rlay schema is stored
  namespace: 'my-app' // selecting the right registry
});

Write to registry

(async () => {
  // writing the schema to the redis registry
  await rlaySchemaRegistry.writeSchemaFromClient(rlayClient);
  // writeSchemaFromClient uses the low-level methods
  // .writeSchemaCids and .writeSchemaPayloads under the hood.
})();

Read and update client

const emptyRlayClient = new Client();

(async () => {
  // fetching the schema cids and payloads from the registry
  // and passing it to the empty rlay client
  await rlaySchemaRegistry.writeSchemaFromClient(emptyRlayClient);
  // emptyRlayClient is now indistinguishable from the auto generated rlayClient
  // from the example before.
  // assert.deepEqual(emptyRlayClient, rlayClient); -> would return true
  // writeSchemaFromClient uses the low-level methods
  // .readSchemaCids and .readSchemaPayloads under the hood.
})();