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

tk-queue

v1.2.2

Published

```

Downloads

6

Readme

TechKids Edu Rabbit Queue

User guide

Connect


import { connect as tkQueueConnect } from 'tk-queue';
const queueUri = `amqp://${rabbitConfig.USERNAME}:${rabbitConfig.PASSWORD}@${rabbitConfig.HOST}:${rabbitConfig.PORT}`
tkQueueConnect(queueUri);

Producer

import { RbProducer } from 'tk-queue';
// Initialize
const rbUserProducer = RbProducer('user');

// Send message when connection is ready
rbUserProducer.send('upsert', <new user data>);

Consumer

// Initialize
import { RbConsumer } from 'tk-queue';

const rbUserConsumer = new RbConsumer(
  "tk-lm",
  "user",
  (data) => new Promise((resolve, reject) => {
    // Upsert user here
    resolve();
  }),
  (_id) => new Promise((resolve, reject) => {
    // Delete user here
    resolve();
  })

// Listen when connection is ready
rbUserConsumer.listen();

Note

Queue design:

  • Some keywords:
    • A producer is a user application that sends messages.
    • A queue is a buffer that stores messages.
    • A consumer is a user application that receives messages.
    • An exchange is a very simple thing. On one side it receives messages from producers and the other side it pushes them to queues.
  • Each service occupies one and only one queue, (e.g. tk-lm-service, tk-hr-service, tk-crm,...)
  • Each resource occupies one and only one exchange, (e.g. course, user, registration,...), has only one producer and multi consumer.
  • Related tutorial about how all that things work together: Read

Message format:

  • type: Operation type (e.g. upsert, delete)
  • data: The udpated data

If there is problem with message in queue, the team should treat it as very critical issuse, thus stop whatever they are doing to fix it

Developer guide

Develop

index.ts: The whole lib

Publish

{
  "name": "tk-queue",
  "version": "x.x.x",
  ...
}
  • Build npm run build

  • Publish npm publish