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

quidproquo-actionprocessor-awslambda

v0.1.30

Published

The AWS runtime for [quidproquo](https://github.com/qpqjs/quidproquo).

Readme

quidproquo-actionprocessor-awslambda

The AWS runtime for quidproquo.

A qpq story yields actions, and a processor is the function that actually carries one out. This package maps the qpq action catalogue onto AWS services, and supplies the Lambda handlers that turn an AWS event into a story execution.

You do not usually install this yourself. It arrives as a dependency of quidproquo-deploy-awscdk and the CLI.

Actions to services

| Action domain | AWS service | | --- | --- | | keyValueStore | DynamoDB | | file | S3 | | userDirectory | Cognito | | queue | SQS | | eventBus | SNS | | email | SES v2 | | config | SSM Parameter Store and Secrets Manager | | crypto | KMS | | ai | Bedrock | | graphDatabase | Neptune, over openCypher | | metric | CloudWatch, written as embedded metric format log lines rather than api calls |

Everything platform-neutral (dates, guids, http, logging) comes from quidproquo-actionprocessor-js, and the Node-specific pieces from quidproquo-actionprocessor-node.

Lambda entry points

The handlers in src/lambdas/ are the other half of the package. Each one adapts a specific AWS event into a story run: API Gateway requests and websocket frames, CloudFront viewer and origin requests, S3 object events, SQS messages, DynamoDB streams, EventBridge schedules and deploy hooks, and the Cognito trigger set for custom auth flows.

There is also a dynamic module loader, which lets a Lambda pull the service's business logic at runtime instead of baking it into the deployment package. That keeps functions warm across deploys and makes rollbacks close to instant.

Naming and config

awsNamingUtils derives every resource name from the account, region, and qpq config, so names are consistent between what the CDK package creates and what the processors look up at runtime. Nothing needs to be passed by hand between the two.

Status

Pre-1.0. The whole quidproquo-* family releases in lockstep, so versions that share a number were built and tested together. Expect APIs to move between releases, and pin your versions.

Documentation

docs.quidproquojs.com

License

MIT. See LICENSE.