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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ts-wire/messaging

v0.1.0

Published

In-process message consumer for ts-wire.

Readme

@ts-wire/messaging

In-process message consumer for ts-wire.

npm install @ts-wire/messaging

Setup

import { TsMessaging } from '@ts-wire/messaging';
import { OrderConsumer } from './consumers/order.consumer';
import { components } from './components';

const messaging = new TsMessaging();
messaging.start({
  consumers: [OrderConsumer],
  components,
});

Stop all consumers cleanly:

await messaging.stop();

@Consumer(topic)

Declares a consumer class for the given topic.

import { Consumer, OnMessage, ConsumerMessage } from '@ts-wire/messaging';

@Consumer('order.created')
export class OrderConsumer {
  @OnMessage()
  async handle(message: ConsumerMessage, { orderService }: Components) {
    await orderService.process(message.payload);
    message.ack();
  }
}

@OnMessage()

Marks the method that handles incoming messages. One per consumer class.

Handler signature:

(message: ConsumerMessage, components: Components) => void | Promise<void>

ConsumerMessage

interface ConsumerMessage {
  topic:   string;
  payload: unknown;
  ack:     () => void;
  nack:    (requeue?: boolean) => void;
}

@ConsumerWith(components)

Injects additional components at class or method level. Method-level overrides class-level for the same key.

@Consumer('user.import')
@ConsumerWith({ db: components.db })
export class UserImportConsumer {
  @OnMessage()
  @ConsumerWith({ email: components.email })
  async handle(message: ConsumerMessage, { db, email }: any) {
    const user = await db.insert(message.payload);
    await email.send(user.email, 'Welcome');
    message.ack();
  }
}

Publishing messages

messaging.publish() dispatches in-process. Useful for testing and internal triggers — not a replacement for a real message broker.

await messaging.publish('order.created', { id: 42, total: 99.90 });

Same service, multiple entry points

// consumers/order.consumer.ts — queue trigger
@Consumer('order.created')
export class OrderConsumer {
  @OnMessage()
  async handle(msg: ConsumerMessage, { orderService }: Components) {
    await orderService.process(msg.payload);
    msg.ack();
  }
}

// controllers/order.controller.ts — HTTP trigger
@Controller('/orders')
export class OrderController {
  @Post('/')
  async create(req: Request, res: Response, { orderService }: Components) {
    const order = await orderService.process(req.body);
    res.status(201).json(order);
  }
}

Same orderService — different entry point. Services know nothing about channels.