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

@naeti/quickserver

v0.4.0

Published

Quick Server — TypeScript framework and init CLI for mobile app prototyping

Readme

Quick API (@naeti/quickserver)

TypeScript API framework with typed routes, inspector, and optional Postgres / Redis / SQS / DynamoDB.

Deployment integrations

| | node-http (default) | aws-lambda | |--|----------------------|--------------| | Entry | server.start() — Hono + Node HTTP | createLambdaHandler(buildApp) — API Gateway HTTP API v2 | | Inspector /_quick | development | disabled | | Background tasks | in-process on start() | not started — use EventBridge / separate Lambdas | | Infra in dev | Docker testcontainers | env only (DATABASE_URL, SQS_*, …) | | DB migrations on connect | yes | deploy-time by default; RUN_MIGRATIONS_ON_COLD_START=true optional |

// app.ts
export async function buildApp() {
  const isLambda = Boolean(process.env.AWS_LAMBDA_FUNCTION_NAME);
  return quickserver.builder()
    .mode(isLambda ? "production" : "development")
    .integration(isLambda ? "aws-lambda" : "node-http")
    .routes()
    // ...
    .build();
}
// lambda.ts
import { createLambdaHandler } from "@naeti/quickserver";
import { buildApp } from "./app.js";
export const handler = createLambdaHandler(buildApp);
# AWS Lambda
quickserver export lambda
pnpm build
sam build && sam deploy

# Node HTTP (Docker)
quickserver export node-http
pnpm build
docker compose up --build

Preview deploy wiring without writing files: build({ dryRun: true }) then server.dryRun().

CLI

npx @naeti/quickserver@latest init my-app
# interactive: deploy target (node-http | aws-lambda) + feature checkboxes

# non-interactive
npx @naeti/quickserver@latest init my-app --yes
npx @naeti/quickserver@latest init my-app --yes \
  --target aws-lambda --features database,queue,recordings \
  --dev-host 127.0.0.1 --dev-mock-user

npx @naeti/quickserver@latest update ./my-app
quickserver export node-http   # Dockerfile + docker-compose.yml
quickserver export lambda      # template.yaml + samconfig.toml

init generates src/app.ts from your choices (infra features, dev bind host, inspector/mock-user/logging, .persistent() for Docker) and writes deploy artifacts. Node HTTP deploy uses docker-compose.yml + .env.docker (not inline env).

Monorepo docs: ../../README.md, builder reference: ../../USAGE.md.