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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@acuris/eventstore-postgresql

v3.0.0

Published

Eventstore implementation storing events in Postgresql

Downloads

11,942

Readme

Postgresql Event store implementation

Eventstore implementation to store events in Postgresql

Running tests

The tests expect a local Postgresql to be running. It uses the standard libpq environment variables to find it. You will need permissions to create schemas (namespaces) in the database that is connected to.

Start a PostgreSQL instance for tests using Docker

In a terminal window, run:

docker run --rm -it -p 5432:5432 -e POSTGRES_HOST_AUTH_METHOD=trust postgres:14-alpine

This runs a PostgreSQL on port 5432 (the default), with password authentication disabled (which is reasonable for local testing). The database is created with a default "postgres" user and database, so you still need to specify this when running tests:

PGUSER=postgres yarn test

Environment variables

The most important variables:

| Name | Description | |------------|:---------------------------------------------------------------------| | PGUSER | User name | | PGPASSWORD | Password | | PGHOST | Server host | | PGPORT | Server port | | PGDATABASE | Database within server to connect to (defaults to same as user name) |

The full list is at https://www.postgresql.org/docs/current/libpq-envars.html

Connecting to an AWS RDS instance

The library includes a helper for connecting to an AWS RDS instance with IAM auth. In order to run the test for this, you need to set two additional environment variables:

| Name | Description | |------------|:---------------------------------------------------------------------| | AWS_REGION | AWS region of an RDS database for testing | | AWS_URL | URL of RDS database: pg://user@hostname/database |

By contrast, these tests are not run if the environment variables are not set.

Releasing a new version

yarn version --patch
git push --tags origin main