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

@noego/dinner

v2.4.1

Published

Portable v1 backend executor

Readme

@noego/dinner

Portable backend executor for noego projects. @noego/app compiles an OpenAPI document (paths, x-controller / x-action, x-middleware, schemas) into an executable binding; dinner turns that binding into a (request: Request, context) => Promise<Response> application that runs unchanged on Node and Cloudflare Workers.

import { createBackendApplication } from '@noego/dinner';

const application = createBackendApplication(binding, {
  contextBuilder,     // per-request scoped IoC container
  controllerBuilder,  // DI-instantiate the controller class
});

Controllers are classes; an action receives an Express-ish compat pair:

import type { CompatRequest, CompatResponse } from '@noego/dinner';

export default class TodosController {
  async getTodos({ req, res }: { req: CompatRequest; res: CompatResponse }) {
    return res.json({ items: [] });
  }
}

Request validation uses Ajv against the operation schemas; builds may supply precompiled standalone validators (route.validators) for runtimes that forbid code generation (Workers).

Portable middleware uses this contract:

type PortableMiddleware = (
  context: BackendRequestContext,
  next: () => Promise<Response | void>,
) => Response | void | Promise<Response | void>;

Middleware may return a Response, await and return next(), or return nothing when the surrounding pipeline is responsible for the final response.

Error replies (exposeErrors, onDefect)

Anything thrown inside a matched request (middleware, controller, hooks, IoC scope) and dinner's own configuration 500s (missing x-action, unknown action, unbound/unresolvable controller) become a 500 JSON reply. Whether that reply carries the real message is decided by exposeErrors, resolved once when createBackendApplication is called:

  1. exposeErrors: true | false passed to createBackendApplication wins.
  2. Otherwise NODE_ENV, read at runtime from process.env (a bundler define of process.env.NODE_ENV is not seen — pass exposeErrors instead): development or test exposes; any other value (production, staging, ...) hides.
  3. Otherwise (NODE_ENV unset, no process at all — Cloudflare Workers without nodejs_compat, browsers — or an env read that throws, e.g. Deno without --allow-env) messages are hidden.

| | reply body | |---|---| | exposed | { "error": true, "message": "<error.message>", "statusCode": 500 } (plus cleanupFailures if an owned request scope failed to close) | | hidden | { "error": true, "message": "Internal Server Error", "statusCode": 500 } |

The real error is always written server-side with console.error ([dinner] GET /route: unhandled error ...), whatever the flag says.

onDefect(error, context) is called for thrown failures (not the configuration 500s, not 400s — those go to onRequestError) before the default reply is built. Return a Response to shape the reply, or nothing for the default 500. A throwing onDefect is logged and falls back to the default 500.

createBackendApplication(binding, {
  exposeErrors: env.NODE_ENV === 'development', // optional: overrides NODE_ENV detection
  onDefect: (error, context) => Response.json({ code: 'INTERNAL' }, { status: 500 }),
});

Exports: createBackendApplication, computeOperationSchemas, VALIDATION_AJV_OPTIONS, createCompatPair, matchRoute, allowedMethods, and the binding/route types.