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

@dra2020/memsqs

v1.0.56

Published

Client and server for in-memory simple queuing service ala AWS SQS.

Downloads

3

Readme

memsqs

Client and server for in-memory simple queuing service ala AWS SQS Fifo queue.

This provides an http service that responds to requests to send, receive and remove messages from any number of queues.

Clients send and receive from the service.

Each message should provide a unique message ID.

Messages are delivered in the order received from the queuing service.

Each message can optionally provide a group ID.

There is a convenient semantics that once a client has received a message from a particular group, that group becomes invisible to other clients for a configurable timeout until any received messages have been removed from the queue.

This can ensure that subsequent messages to that group are all received by the same client while it continues to actively process them.

A client can also explicitly 'claim' a group ID even if messages with that group ID are not flowing through the queue. This prevents another the ownership claim from timing out at the queueing service even when a client wants to continue receiving those messages (because it continues to have allocated resources dedicated to processing it, for example). Ownership claims also age out and need to be renewed explicitly.

Once a message has been received, it should be explicitly removed from the queue. If it is not removed, it will become visible to another client after a configurable timeout.

The special group ID '' can be used to send a multicast to explicitly owned groups in a queue. So each client can claim its own group ID in a queue and messages that are sent to the group ID '' will be exploded to be sent to each separate group. This provides a mechanism for one or more producers to broadcast to a set of consumers.