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-eslint-config

v0.1.11

Published

eslint config for quidproquo projects.

Readme

eslint config

Not for prod

qpq rules

The shared config bundles a small ESLint plugin (plugin/index.mjs, namespace qpq) that enforces the framework's ask naming contract.

Using the shared config gets you the rules automatically. To use the plugin on its own, without the rest of the config:

// eslint.config.mjs
import { qpqPlugin } from 'quidproquo-eslint-config';

export default [
  qpqPlugin.configs.recommended,
  // or pick rules individually:
  // { plugins: { qpq: qpqPlugin }, rules: { 'qpq/require-yield-star': 'error' } },
];

The rules:

qpq/require-yield-star

Inside a generator, a call to any ask* function (including obj.askX()) must be delegated with yield*. A bare call or a plain yield creates a generator that never runs. Auto-fixable: the fix inserts yield* (adding parentheses where a bare yield expression is not allowed), upgrades yield to yield*, and replaces a wrong await.

const now = askDateNow();        // error, fixed to: yield* askDateNow()
const now = yield askDateNow();  // error, fixed to: yield* askDateNow()
const now = yield* askDateNow(); // correct

Allowed without yield*:

  • ask calls passed as arguments, that's how stories compose: yield* askRunParallel([askA(), askB()]), runStory(askDateNow(), mocks)
  • ask calls outside generator functions (test drivers, forwarding wrappers), since yielding is not possible there anyway

qpq/ask-prefix-generator-only

The ask prefix is reserved for qpq stories, the same way use is reserved for React hooks. Any function literal named ask* (declaration, arrow, method, class property) must be a generator. Aliases and factory results like const askRead = createContextReader(ctx) are fine because they are not function literals. Not auto-fixable, rename the function or make it a generator.

Tests live next to the rules (plugin/rules/*.test.mjs) and run with the repo's vitest suite: npx vitest run --project quidproquo-eslint-config.