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

@ez4/database

v0.50.0

Published

EZ4: Components to build database services

Downloads

753

Readme

EZ4: Database

The Database contract defines a database service for your application. It uses EZ4's reflection system to analyze your engine, tables, indexes, relations, and scalability configuration, then generates the infrastructure and runtime bindings required to store and query data.

Getting started

Install

npm install @ez4/database @ez4/local-database @ez4/aws-aurora -D

You can use @ez4/aws-dynamodb instead of @ez4/aws-aurora for NoSQL database.

Create database

Here's a minimal example of a database service with a single table.

import type { Environment, Service } from '@ez4/common';
import type { Database } from '@ez4/database';

// MyDb table
type MyTableSchema = {
  foo: string;
  bar: number;
};

// MyDb declaration
export declare class MyDb extends Database.Service<PostgresEngine> {
  client: Client<MyDb>;

  tables: [
    Database.UseTable<{
      name: 'test_table';
      schema: MyTableSchema;
      indexes: {
        foo: Index.Primary;
      };
    }>
  ];
}

Use database

Any handler with access to the database service can perform queries.

import type { Service } from '@ez4/common';
import type { MyDb } from './db';

// Any other handler that has injected MyDb service
export async function anotherHandler(_request: any, context: Service.Context<AnotherService>) {
  const { myDb } = context;

  // Insert one record
  await myDb.test_table.insertOne({
    data: {
      foo: 'foo',
      bar: 123
    }
  });

  // Find one record
  const result = await myDb.test_table.findOne({
    select: {
      bar: true
    },
    where: {
      foo: 'foo'
    }
  });
}

With your database service defined, EZ4 handles provisioning, migrations, scaling, and runtime wiring automatically according to your contract.

Database properties

Service

| Name | Type | Description | | ----------- | ------------------------- | ----------------------------------------------------- | | scalability | Database.UseScalability<> | Scalability configuration. | | tables | Database.UseTable<> | Defines all tables available in the database service. | | engine | Database.UseEngine<> | Determines which database engine to use. | | variables | object | Environment variables associated with all streams. | | services | object | Injected services associated with all streams. |

Use type helpers for scalability and tables properties.

Tables

| Name | Type | Description | | --------- | ------------------------- | --------------------------- | | stream | Database.UseTableStream<> | Table stream configuration. | | name | string | Table name. | | schema | object | Table schema. | | relations | object | Table relations. | | indexes | object | Table indexes. |

Streams (DynamoDB only)

| Name | Type | Description | | ------------ | ---------------- | ----------------------------------------------------------- | | listener | function | Life-cycle listener function for the stream. | | handler | function | Entry-point handler function for the stream. | | variables | object | Environment variables associated with the stream. | | logRetention | integer | Log retention (in days) for the handler. | | logLevel | LogLevel | Log level for the handler. | | architecture | ArchitectureType | Architecture type for the cloud function. | | runtime | RuntimeType | Runtime for the cloud function. | | files | string[] | Additional resource files added into the handler bundle. | | memory | integer | Memory available (in megabytes) for the handler. | | timeout | integer | Max execution time (in seconds) for the handler. | | debug | boolean | Determine whether the debug mode is active for the handler. | | vpc | boolean | Determines whether or not VPC is enabled for the handler. |

Streams is a DynamoDB feature, thus unavailable for Aurora Postgres.

Examples

Providers

License

MIT License