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

@uns-kit/database

v2.0.51

Published

Database helpers for UNS services with config-driven connections, SQL file loading, and portable named-parameter compilation.

Readme

@uns-kit/database

Database helpers for UNS services. The package keeps database access outside @uns-kit/core while still fitting the same config/secret-resolution flow used by the rest of uns-kit.

Installation

Install the package plus only the driver(s) you need:

pnpm add @uns-kit/database pg
# or
pnpm add @uns-kit/database better-sqlite3
# or
pnpm add @uns-kit/database oracledb

pnpm add @uns-kit/database pg is the intended one-command install pattern for Postgres support. Replace pg with oracledb or better-sqlite3 for the other drivers.

What it provides

  • Driver-aware client factory for pg, sqlite, and oracle
  • One portable SQL parameter style for all drivers: write SQL with :namedParams
  • Shared database manager for multiple named connections
  • SQL file loading from a configured sqlDir
  • Zod schemas for app-level databases config extensions

Config schema integration

Inside your app's src/config/project.config.extension.ts:

import { z } from "zod";
import { databasesConfigSchema } from "@uns-kit/database";

export const projectExtrasSchema = z.object({
  databases: databasesConfigSchema,
});

The schema uses the same placeholder object shapes as @uns-kit/core, so ConfigFile.loadConfig() resolves database secrets automatically.

Example config

{
  "databases": {
    "main": {
      "dialect": "pg",
      "host": { "provider": "external", "key": "PG_HOST" },
      "port": 5432,
      "database": "factory",
      "user": "app_user",
      "password": { "provider": "env", "key": "PG_PASSWORD" },
      "usePool": true,
      "sqlDir": "./sql"
    }
  }
}

Set "usePool": false for Postgres or Oracle when you want a direct non-pooled connection, matching the old local proxy behavior.

Usage

import { ConfigFile } from "@uns-kit/core";
import { registerDatabase } from "@uns-kit/database";

const config = await ConfigFile.loadConfig();
registerDatabase("main", config.databases.main);
registerDatabase("reporting", config.databases.reporting);
registerDatabase("mesOracle", config.databases.mesOracle);

Then in another file:

import { getDatabase } from "@uns-kit/database";

const db = await getDatabase("main");
const rows = await db.queryFile("queries/get-orders.sql", {
  lineId: "L1",
  fromTs: "2026-05-20T08:00:00Z",
});

Use :lineId, :fromTs, etc. in SQL files. The package compiles them to $1, ?, or Oracle bind syntax depending on the selected driver. The authoring style stays the same for all supported databases: plain SQL plus :namedParam bindings.

See also: