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-webserver

v0.1.25

Published

The web layer of [quidproquo](https://github.com/qpqjs/quidproquo). It adds everything a service needs to be reachable over the network: routes, apis, websockets, dns, email, and the config settings that describe them.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

joecoadyjoecoady

Keywords

Readme

quidproquo-webserver

The web layer of quidproquo. It adds everything a service needs to be reachable over the network: routes, apis, websockets, dns, email, and the config settings that describe them.

Most applications should install quidproquo, which re-exports this package together with quidproquo-core.

npm install quidproquo-webserver

What it adds

Actions for the things a web service does, on top of the core catalogue:

| Domain | Covers | | --- | --- | | api | Calling another service's api | | webEntry | Serving a website or single page app | | websocket | Sending messages to connected clients | | email | Sending mail | | dns | Record lookups and management | | serviceFunction | Invoking a function on another service | | routeAuthValidation, apiKeyValidation | Auth and api key checks in front of a route | | genericDataResource, admin | Data resources and the admin surface |

Config settings in src/config/settings/, the define* helpers you compose into a service config: defineRoute, defineApi, defineWebEntry, defineWebsocket, defineDns, defineCertificate, defineEmailSender, defineApiKey, defineCache, defineSeo, defineSeed, defineMigration, defineDomainProxy, defineSubdomainRedirect, defineServiceFunction, and the auth system helpers.

A service config is a plain array. The deploy packages read it to build infrastructure, and the dev server reads the same array to run the service locally.

qpqWebServerUtils, the helpers you use inside route stories, for example toJsonEventResponse for turning a value into an HTTPEventResponse.

Where the platform bits live

This package stays platform-neutral. Anything that is specific to one cloud lives in the layer that owns it: quidproquo-config-aws for AWS-only settings, and the quidproquo-actionprocessor-* packages for the implementations that run these actions.

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.