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

@empilha/pg

v0.2.4

Published

Integração PostgreSQL para o framework Empilha usando pg.

Readme

@empilha/pg

Integra PostgreSQL (pg) ao Empilha sem acoplar o framework principal ao driver.

import { createApplication, defineModule } from "empilha";
import { postgres } from "@empilha/pg";

const app = await createApplication(
  defineModule({
    name: "app",
    controllers: [UserController],
    plugins: [
      postgres({
        url: process.env.DATABASE_URL!,
        sql: "./src/queries",
        timeout: 5_000,
      }),
    ],
  }),
);

timeout configura query_timeout e statement_timeout no pg, além do timeout das operações do Empilha. O plugin executa as queries por um client dedicado para que o AbortSignal também possa cancelar uma query em andamento no PostgreSQL.

Runners e pools sem queryWithOptions executam com timeout apenas de parede: a requisição recebe 504 quando o limite é atingido, enquanto a operação já entregue ao driver pode terminar depois. Use @empilha/pg quando o cancelamento real da query for necessário.

Se a aplicação fornecer um runner próprio, o método query() deve observar o options.signal. Um runner que ignora o sinal ainda pode continuar executando até o próprio timeout do driver, mesmo depois de a requisição receber 504. Pools gerenciados passados diretamente a app.postgres() também são aceitos sem queryWithOptions; nesse caso, o timeout do framework é apenas de parede. Para cancelamento real, exponha queryWithOptions ou use @empilha/pg. Se o driver já possui seu próprio limite, você pode desabilitar o timeout do framework com { timeout: null }.