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

@adizen/events-hub-sdk

v0.1.4

Published

Official client SDK for triggering Events Hub workflows from any app

Downloads

277

Readme

@events-hub/sdk

Official TypeScript/JavaScript client for sending events to an Events Hub deployment. It wraps the HTTP API exposed by the NestJS backend so any application can trigger events with type safety and consistent headers.

Installation

npm install @events-hub/sdk
# or
yarn add @events-hub/sdk

Quick start

import { EventsHubClient } from "@events-hub/sdk";

const client = new EventsHubClient({
  baseUrl: "https://events.mycompany.com",
  apiKey: process.env.EVENTS_HUB_KEY,
});

await client.trigger("user.signed_up", {
  userId: "123",
  email: "[email protected]",
});

Options

await client.trigger("order.created", orderPayload, {
  userId: "user-42",
  metadata: { source: "checkout" },
});

await client.triggerDelayed("invoice.send", invoicePayload, 10_000);

await client.triggerScheduled(
  "reports.daily",
  { workspaceId: "acme" },
  "0 8 * * *",
);

await client.triggerBatch([
  { name: "user.signup", data: { email: "[email protected]" } },
  { name: "user.signup", data: { email: "[email protected]" } },
]);

Handler metadata

Need to introspect a handler’s schema? Fetch it through the admin API:

const handler = await client.getHandler("user-signup");
console.log(handler.expectedPayloadSchema);

Configuration

| Option | Description | | --------------- | --------------------------------------------------------------- | | baseUrl | Base URL to your deployed backend (required). | | apiKey | Optional API key. Sent using the x-api-key header by default. | | apiKeyHeader | Override header name if your backend expects a custom header. | | timeoutMs | Axios request timeout (defaults to 10s). | | defaultHeaders| Any extra headers to include in every request. |

Publishing

Use the provided script:

npm run build --workspace=@events-hub/sdk
npm publish --workspace=@events-hub/sdk --access public

Remember to update the version in package.json before publishing. Since this package depends on @events-hub/types, publish the types package first if you make changes to shared definitions.