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

@mhlabs/events-client

v0.0.20

Published

Thin client for Amazon EventBridge with support for a metadata/data message pattern

Downloads

3

Readme

@mhlabs/events-client

Node.js CI

This is still under development and should not be used in production code

A thin client for Amazon EventBridge that has as purpose to enforce a message pattern convention following this contract:

{
    "source": "my-source",
    "detail-type": "my-detail-type"
    ...,
    "detail": {
        "metadata": {
            ...
        },
        "data": {
            ... 
        }
    }
}

If an event originates from a DynamoDB event, the new and old image will be added under data along with a JSON diff under metadata:

{
    "source": "my-source",
    "detail-type": "my-detail-type"
    ...,
    "detail": {
        "metadata": {
            "diff": {
                "Price": [3, 5]
            },
            "action": "update"
        },
        "data": {
            {
                "old": {
                    "Id": "123",
                    "Price": 3
                },
                "new": {
                    "Id": "123",
                    "Price": 5
                }
            }
        }
    }
}

The JSON diff will only be added if both old and new are assigend.

If old is null and new is assigned, then metadata.action will be set to create.

If new is null and old is assigned, then metadata.action will be set to delete.

Usage

npm install --save @mhlabs/events-client

const events = require("@mhlabs/events-client");
const client = new events.Client(eventBridgeClient, eventBusName, source);

All constructor arguments are optional and defaults to:

  • eventBridgeClient: new AWS.EventBridgeClient()
  • eventBusName: "default"
  • source: `process.env.StackName

This is intended to run in AWS Lambda and will by default use the CloudFormation stack's name, as source.

To send a single event:

const eventDetail = { id: 123, value: 10 }
await client.send("my-detail-type", eventDetail);

To send multiple events. Max 10 per batch:

const eventDetail = [{ id: 123, value: 10 }, { id: 234, value: 15 }]
await client.send("my-detail-type", eventDetail);

To send DynamoDB events from a lambda trigger:

async function handler(dynamoDbEvent, context) {
    await client.send("my-detail-type", dynamoDbEvent);
}