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

@luxledger/http

v0.5.0

Published

Framework-agnostic HTTP contracts, schemas, mappers, and OpenAPI source for LuxLedger.

Readme

@luxledger/http

HTTP mapping helpers for @luxledger/core domain/application errors.

Boundaries

  • Owns transport contracts and route-level reusable error response specs.
  • Maps domain/application errors to transport-safe HTTP DTOs.
  • Accepts the stable domain-error shape across bundled public export identities while rejecting raw database/unknown errors as non-leaking 500 INTERNAL_ERROR responses.
  • Contains no HTTP server runtime code and no persistence code.
  • Reads no environment variables; JWT, rate limiting, port, and lifecycle configuration belong to the host application.

Forbidden dependencies

  • No framework runtime deps (for example: fastify, express, nestjs).
  • No adapter/runtime deps (for example: drizzle-orm, postgres).
  • Keep dependency direction: can depend on @luxledger/core, never on apps/*.

Public API

  • @luxledger/http:
    • mapDomainErrorToHttp
    • errorResponseSchema
    • defaultErrorResponses
    • readWhereParameter, typed list-filter field maps, and URL-encoded JSON schema helpers
    • HttpErrorDto, HttpErrorMapper, ErrorResponse types
  • @luxledger/http/errors: schema and response contracts
  • @luxledger/http/errors: error mapping
  • @luxledger/http/route-specs: default route error response specs

Usage

import { defaultErrorResponses, mapDomainErrorToHttp } from '@luxledger/http';

const dto = mapDomainErrorToHttp(error);
reply.code(dto.statusCode).send(dto);
route.schema.response = { ...defaultErrorResponses };
import { errorResponseSchema } from '@luxledger/http/errors';

Canonical contract

The source-of-truth HTTP contract is openapi/openapi.yaml. Runtime contract definitions and OpenAPI must change together and pass bun run contract:verify. See the repository integration guide for host responsibilities and conventions.

The shared statement contracts cover GET /v1/accounts/{id}/statement and GET /v1/accounts/{id}/credit-statement; both require explicit from and as_of boundaries and use the common opaque cursor/limit contract.

Scoped list endpoints accept an optional where query parameter containing URL-encoded JSON. For example, ?where=%7B%22balance_minor%22%3A%7B%22gte%22%3A%220%22%7D%7D filters accounts whose balance is at least zero. Filters are ANDed, use only each endpoint's documented public fields, and support eq, ne, in plus numeric/date comparisons where applicable. The decoded value is limited to 8 KiB; in accepts 1–100 non-null values. Omit where or pass {} for no additional filter. Invalid JSON, repeated parameters, unknown fields/operators, and invalid types return the shared 400 INVALID_INPUT response. Date-time filter values require a timezone and must be exactly representable in milliseconds. Extra fractional digits are accepted only when zero (for example, .123000Z); values such as .123001Z return 400 INVALID_INPUT instead of silently changing the comparison boundary.

Paginated list endpoints accept limit (default 50, maximum 200) and an opaque cursor, and return { data, next_cursor }. Reconciliation results can be fetched from GET /v1/reconciliation/runs/{id}/results with typed where filters.

Before production use, cross-check this README against the OpenAPI shipped with the installed package version and review the documentation publication checklist.