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

@funcd-dev/drizzle

v0.24.0

Published

Drizzle over funcd's context.sql: the sqlite-proxy database and drizzle-kit migrations applied in one execute

Readme

@funcd-dev/drizzle

Drizzle over funcd's context.sql (funcd ADR-0258): one package instead of a copied adapter in each App.

import { applyMigrations, funcdDrizzle } from '@funcd-dev/drizzle';
import type { FunctionContext } from '@funcd-dev/shim';

import * as schema from './db/schema.ts';

export const db = (ctx: FunctionContext) => funcdDrizzle(ctx, { schema });

// the migrate function, or an App's preApply hook: the drizzle-kit folder the bundle carries
const migrations: Record<string, string> = import.meta.glob(['../../drizzle/*.sql', '../../drizzle/meta/_journal.json'], {
  query: '?raw',
  import: 'default',
  eager: true,
});
export const handle = async (ctx: FunctionContext) => ({ applied: await applyMigrations(ctx, migrations) });
  • funcdDrizzle(ctx, { alias = 'app', schema }) is Drizzle's sqlite-proxy database. A SELECT or WITH goes to context.sql.queryValues, any other statement to execute, since Drizzle sends insert … returning() as a read. A batch is one execute, all or nothing, and is for writes: a select inside it gets no rows. A WITH that writes (db.with(cte).insert(…)) takes the read path too, so write without a WITH.
  • applyMigrations(ctx, files, { alias = 'app', table = '_migrations' }) applies the drizzle-kit migrations the table lacks, with their rows, in one execute, and returns how many it applied. It reads them from files, a path to content map, and keeps the table as Drizzle's own sqlite-proxy migrator keeps it, so either one can take over from the other.
  • drizzle-orm is a peer dependency: the App picks its version (>=0.45.0 <1.0.0).