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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sanctumlabs/messageschema

v0.9.0

Published

Shared message schemas for Sanctum Labs Platform

Readme

Message Schema JavaScript library

Message schema library in JavaScript. This can be used as the canonical way of carrying message data or event data in a platform between services in a distributed architecture. This is especially useful in an event driven architecture setup where events are how services communicate with each other.

Setup

First ensure you have npm installed locally or yarn.

npm install

Or

yarn install

Or you can execute the above with make:

make install

This will install the dependencies defined in the package.json file in a node_modules directory.

That should be it.

In order to build a package, the protobuf generated code needs to be build first. This can be done from the root directory of this project with:

buf generate

Or

make generate

Now, the package can be built with:

make build

Other commands can be viewed with:

make help

Publication

Since publication is to 3 registries, we rely on the CI to handle the publication of this package. Gitlab CI handles publication to Gitlab NPM package registry while Github workflows publishes to both NPM registry and Github NPM Registry.

Note that the secrets and configuration to publish to these registries are available as secrets in the CI environment and are not pushed to a VCS.

There is a blank .npmrc file that is populated by the CI in order to ensure that the package is published to the appropriate NPM package registry