@tickernelz/wardmote-db 0.0.0 → 2026.1108.2

package/node_modules/async-exit-hook/package.json

@@ -0,0 +1,66 @@
+{
+  "name": "async-exit-hook",
+  "version": "2.0.1",
+  "description": "Run some code when the process exits (supports async hooks and pm2 clustering)",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/tapppi/async-exit-hook.git"
+  },
+  "author": {
+    "name": "Tapani Moilanen",
+    "email": "moilanen.tapani@gmail.com",
+    "url": "https://github.com/tapppi"
+  },
+  "contributors": [
+    {
+      "name": "Sindre Sorhus",
+      "email": "sindresorhus@gmail.com",
+      "url": "http://sindresorhus.com"
+    }
+  ],
+  "engines": {
+    "node": ">=0.12.0"
+  },
+  "scripts": {
+    "test": "xo && nyc ava",
+    "release": "standard-version"
+  },
+  "files": [
+    "index.js"
+  ],
+  "keywords": [
+    "exit",
+    "quit",
+    "process",
+    "hook",
+    "graceful",
+    "handler",
+    "shutdown",
+    "sigterm",
+    "sigint",
+    "sighup",
+    "pm2",
+    "cluster",
+    "child",
+    "reload",
+    "async",
+    "terminate",
+    "kill",
+    "stop",
+    "event"
+  ],
+  "devDependencies": {
+    "ava": "^0.21.0",
+    "coveralls": "^2.11.14",
+    "nyc": "^10.3.2",
+    "standard-version": "^4.2.0",
+    "xo": "^0.18.2"
+  },
+  "ava": {
+    "files": [
+      "test/*.js",
+      "!tests/cases/*"
+    ]
+  }
+}

package/node_modules/async-exit-hook/readme.md

@@ -0,0 +1,118 @@
+# async-exit-hook
+[![Build Status](https://api.travis-ci.org/Tapppi/async-exit-hook.svg)](https://travis-ci.org/Tapppi/async-exit-hook)
+[![Coverage Status](https://coveralls.io/repos/github/Tapppi/async-exit-hook/badge.svg?branch=master)](https://coveralls.io/github/Tapppi/async-exit-hook?branch=master)
+
+> Run some code when the process exits
+
+The `process.on('exit')` event doesn't catch all the ways a process can exit. This module catches:
+
+* process SIGINT, SIGTERM and SIGHUP, SIGBREAK signals  
+* process beforeExit and exit events  
+* PM2 clustering process shutdown message ([PM2 graceful reload](http://pm2.keymetrics.io/docs/usage/cluster-mode/#graceful-reload))  
+
+Useful for cleaning up. You can also include async handlers, and add custom events to hook and exit on.
+
+Forked and pretty much rewritten from [exit-hook](https://npmjs.com/package/exit-hook).
+
+
+## Install
+
+```
+$ npm install --save async-exit-hook
+```
+
+## Usage
+
+### Considerations and warning
+#### On `process.exit()` and asynchronous code
+**If you use asynchronous exit hooks, DO NOT use `process.exit()` to exit.
+The `exit` event DOES NOT support asynchronous code.**
+>['beforeExit' is not emitted for conditions causing explicit termination, such as process.exit()]
+(https://nodejs.org/api/process.html#process_event_beforeexit)
+
+#### Windows and `process.kill(signal)`
+On windows `process.kill(signal)` immediately kills the process, and does not fire signal events, 
+and as such, cannot be used to gracefully exit. See *Clustering and child processes* for a
+workaround when killing child processes. I'm planning to support gracefully exiting 
+with async support on windows soon.
+
+### Clustering and child processes
+If you use custom clustering / child processes, you can gracefully shutdown your child process
+by sending a shutdown message (`childProc.send('shutdown')`).
+
+### Example
+```js
+const exitHook = require('async-exit-hook');
+
+exitHook(() => {
+    console.log('exiting');
+});
+
+// you can add multiple hooks, even across files
+exitHook(() => {
+    console.log('exiting 2');
+});
+
+// you can add async hooks by accepting a callback
+exitHook(callback => {
+    setTimeout(() => {
+        console.log('exiting 3');
+        callback();
+    }, 1000);
+});
+
+// You can hook uncaught errors with uncaughtExceptionHandler(), consequently adding 
+// async support to uncaught errors (normally uncaught errors result in a synchronous exit).
+exitHook.uncaughtExceptionHandler(err => {
+    console.error(err);
+});
+
+// You can hook unhandled rejections with unhandledRejectionHandler()
+exitHook.unhandledRejectionHandler(err => {
+    console.error(err);
+});
+
+// You can add multiple uncaught error handlers
+// Add the second parameter (callback) to indicate async hooks
+exitHook.uncaughtExceptionHandler((err, callback) => {
+    sendErrorToCloudOrWhatever(err) // Returns promise
+        .then(() => { 
+             console.log('Sent err to cloud'); 
+         });
+        .catch(sendError => {
+             console.error('Error sending to cloud: ', err.stack));
+        })
+        .then(() => callback);
+    });
+});
+
+// Add exit hooks for a signal or custom message:
+
+// Custom signal
+// Arguments are `signal, exitCode` (SIGBREAK is already handled, this is an example)
+exitHook.hookEvent('SIGBREAK', 21);
+
+// process event: `message` with a filter
+// filter gets all arguments passed to *handler*: `process.on(message, *handler*)`
+// Exits on process event `message` with msg `customShutdownMessage` only
+exitHook.hookEvent('message', 0, msg => msg !== 'customShutdownMessage');
+
+// All async hooks will work with uncaught errors when you have specified an uncaughtExceptionHandler
+throw new Error('awesome');
+
+//=> // Sync uncaughtExcpetion hooks called and retun
+//=> '[Error: awesome]'
+//=> // Sync hooks called and retun
+//=> 'exiting'
+//=> 'exiting 2'
+//=> // Async uncaughtException hooks return
+//=> 'Sent error to cloud'
+//=> // Sync uncaughtException hooks return
+//=> 'exiting 3'
+```
+
+
+## License
+
+MIT © Tapani Moilanen  
+MIT © [Sindre Sorhus](http://sindresorhus.com)

package/node_modules/embedded-postgres/LICENSE.md

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) 2022 Lei Nelissen
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/node_modules/embedded-postgres/README.md

@@ -0,0 +1,191 @@
+![Embedded
+Postgres](https://github.com/leinelissen/embedded-postgres/raw/main/docs/images/embedded-postgres-header.svg)
+
+<div align="center">
+
+![npm](https://img.shields.io/npm/v/embedded-postgres)
+![npm type definitions](https://img.shields.io/npm/types/embedded-postgres)
+![npm](https://img.shields.io/npm/dy/embedded-postgres)
+![NPM](https://img.shields.io/npm/l/embedded-postgres)
+![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/leinelissen/embedded-postgres/test.yml)
+
+
+</div>
+
+<h3 align="center">
+    🐘 A Node package that spawns PostgresQL clusters programatically.
+</h3>
+
+## Installation
+`embedded-postgres` is available from NPM:
+
+```sh
+npm i embedded-postgres
+```
+
+<br />
+
+## Usage
+This package contains a simple API that allows you to create clusters, start
+them, create / delete database and stop any existing processes.
+
+```ts
+import EmbeddedPostgres from 'embedded-postgres';
+
+async function main() {
+    // Create the object
+    const pg = new EmbeddedPostgres({
+        databaseDir: './data/db',
+        user: 'postgres',
+        password: 'password',
+        port: 5432,
+        persistent: true,
+    });
+
+    // Create the cluster config files
+    await pg.initialise();
+
+    // Start the server
+    await pg.start();
+
+    // Create and/or drop database
+    await pg.createDatabase('TEST');
+    await pg.dropDatabase('TEST');
+
+    // Initialize a node-postgres client
+    const client = pg.getPgClient();
+    await client.connect();
+    const result = await client.query('SELECT datname FROM pg_database');
+
+    // Stop the server
+    await pg.stop();
+}
+
+main();
+```
+
+<br />
+
+## PostgresQL Versions
+This package aims to track the [PostgresQL support
+policy](https://www.postgresql.org/support/versioning/) for supported versions.
+Additionally, we track the binaries that are created upstream in [zonky's
+embedded-postgres-binaries](https://github.com/zonkyio/embedded-postgres). This
+leads to the following current support matrix:
+
+| Platform / Architecture   | 12.20.0 | 13.16.0 | 14.13.0 | 15.8.0 | 16.4.0 | 17.0.0 |
+|---------------------------|---------|---------|---------|--------|--------|--------|
+| 🍎 Darwin / x64           | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🍎 Darwin / arm64[[1]](https://github.com/zonkyio/embedded-postgres/issues/86#issuecomment-1120425822) | 🚫 | 🚫 | 🚫 | ✅ | ✅ | ✅ |
+| 🪟 Windows / x64          | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🐧 Linux / x64            | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🐧 Linux / arm            | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🐧 Linux / arm64          | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🐧 Linux / ia32           | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| 🐧 Linux / ppc64          | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+
+In order to install a particular version, look for the latest tag in
+[NPM](https://www.npmjs.com/package/embedded-postgres). For example, if you
+would like to install `v10.20.0`, you can currently use the following tag:
+```sh
+npm i embedded-postgres@10.20.0-beta.6
+```
+
+Installing particular versions of PostgresQL (i.e. versions not released on NPM)
+is currently not possible. If you would have a need for doing so, please create
+an issue.
+
+<br />
+
+## API
+Options in the constructor can be used to modify the behaviour of the
+application. The parameters that are available as part of the options can be
+seen here:
+
+| Property | Type | Description |
+|---|---|---|
+| databaseDir | string | The location where the data should be persisted to. Defaults to `./data/db` |
+| port | number | The port where the Postgres database should be listening. Defaults to:  `5432` |
+| user | string | The username for logging into the Postgres database. Defaults to `postgres` |
+| password | string | The password for logging into the Postgres database. Defaults to `password` |
+| authMethod | 'scram-sha-256' \| 'password' \| 'md5' | The authentication method to use when authenticating against Postgres. Defaults to `password`  |
+| persistent | boolean | Whether all data should be left in place when the database is shut down. Defaults to `true`. |
+| initdbFlags | string[] | Pass any additional flags to the initdb process. You can find all available flags here: https://www.postgresql.org/docs/current/app-initdb.html. Flags should be passed as a string array, e.g. `["--debug"]` or `["--locale=en-GB"]`  Defaults to `[]` 
+| postgresFlags | string[] | Pass any additional flags to the postgres process. You can find all available flags here: https://www.postgresql.org/docs/current/app-postgres.html. Flags should be passed as a string array, e.g. `["--debug"]` or `["--locale=en-GB"]`. Defaults to `[]`.  |
+| createPostgresUser | boolean | Postgres does not allow binaries to be run by root. In case you're running in root-only enviroments, such as Docker containers, you may need to create an extra user on your system in order to be able to call the binaries. <br />NOTE: This WILL irreversibly modify your host system. The effects are somewhat minor, but it's still recommend to only use this in Docker containers. Defaults to `false`. |
+| onLog | (message \| string) => void | Pass in a custom logging handler. This will relay and console messages that are generated by the postgres and initdb processes. Defaults to `console.log` |
+| onError | (messageOrError \| string \| Error \| unknown) => void | Pass in a custom error logging handler. This will catch and stderr results coming in from the postgres and initdb processes. Defaults to `console.error` |
+
+<br />
+
+## Contributing
+This package is open to issues, feedback, ideas and pull requests. Create an
+issue on this repository to get started! In order to get started with
+development, you might need some extra pointers
+
+### Development
+In order to get yourself situated for development, you will need to the
+repository up and running. In order to make this work, start with a relatively
+recent install of NodeJS (at least v18, v20+ recommended). You can then run this
+command to install all packages:
+```
+npm install --force
+```
+
+> [!NOTE]
+> You must include `--force` or else NPM will refuse to install the
+> dependencies for all packages, including those not for the current architecture.
+
+Then, you must pre-compile all Typescript using the following command:
+```
+npm run build
+```
+
+As soon as that is complete, we'll download the requisite PostgresQL binaries
+for your particular architecture using:
+```
+npm run download
+```
+
+Lastly, you can hop over to `packages/embedded-postgres` and do some development
+there:
+```
+cd packages/embedded-postgres
+```
+
+You can force automatic recompliation of the Typescript files by running:
+```
+npm start
+```
+
+Don't forget to add and run tests when you are developing new functionality. Add
+them to `tests/index.test.ts`, and run the tests by running:
+```
+npm test
+```
+
+<br />
+
+## Troubleshotting
+
+### Running in Docker containers
+Running in Docker containers might fail, because many are setup to run with the
+root user as default. Either you resolve to setting up a container with a
+specific user yourself, or you set the `createPostgresUser` option to true,
+after which embedded-postgres will automatically set up a postgres user on the
+system for usage by your script.
+
+<br />
+
+## Credits and Licensing
+Embedded Postgres was created by Lei Nelissen for [BMD
+Studio](https://bmd.studio). It is based on [zonky's
+embedded-postgres-binaries](https://github.com/zonkyio/embedded-postgres). The
+binaries are made available under the Apache License 2.0, whereas the specific
+code in this package is made available under the MIT license.
+
+<a href="https://bmd.studio">
+    <img src="https://github.com/leinelissen/embedded-postgres/raw/main/docs/images/logo-bmd.svg" alt="BMD Studio" width="150" height="150" />
+</a>
+
+<br />

package/node_modules/embedded-postgres/dist/binary.d.ts

@@ -0,0 +1,7 @@
+export declare type PostgresBinaries = {
+    postgres: string;
+    pg_ctl: string;
+    initdb: string;
+};
+declare function getBinaries(): Promise<PostgresBinaries>;
+export default getBinaries;

package/node_modules/embedded-postgres/dist/binary.js

@@ -0,0 +1,41 @@
+import os from 'os';
+function getBinaries() {
+    const arch = os.arch();
+    const platform = os.platform();
+    switch (platform) {
+        case 'darwin':
+            switch (arch) {
+                case 'arm64':
+                    return import('@embedded-postgres/darwin-arm64');
+                case 'x64':
+                    return import('@embedded-postgres/darwin-x64');
+                default:
+                    throw new Error(`Unsupported arch "${arch}" for platform "${platform}"`);
+            }
+        case 'linux':
+            switch (arch) {
+                case 'arm64':
+                    return import('@embedded-postgres/linux-arm64');
+                case 'arm':
+                    return import('@embedded-postgres/linux-arm');
+                case 'ia32':
+                    return import('@embedded-postgres/linux-ia32');
+                case 'ppc64':
+                    return import('@embedded-postgres/linux-ppc64');
+                case 'x64':
+                    return import('@embedded-postgres/linux-x64');
+                default:
+                    throw new Error(`Unsupported arch "${arch}" for platform "${platform}"`);
+            }
+        case 'win32':
+            switch (arch) {
+                case 'x64':
+                    return import('@embedded-postgres/windows-x64');
+                default:
+                    throw new Error(`Unsupported arch "${arch}" for platform "${platform}"`);
+            }
+        default:
+            throw new Error(`Unsupported platform "${platform}"`);
+    }
+}
+export default getBinaries;

package/node_modules/embedded-postgres/dist/index.d.ts

@@ -0,0 +1,58 @@
+import pg from 'pg';
+import { PostgresOptions } from './types.js';
+/**
+ * This class creates an instance from which a single Postgres cluster is
+ * managed. Note that many clusters may be created, but they will need seperate
+ * data directories in order to be properly lifecycle managed.
+ */
+declare class EmbeddedPostgres {
+    protected options: PostgresOptions;
+    private process?;
+    private isRootUser;
+    constructor(options?: Partial<PostgresOptions>);
+    /**
+     * This function needs to be called whenever a Postgres cluster first needs
+     * to be created. It will populate the data directory with the right
+     * settings. If your Postgres cluster is already initialised, you don't need
+     * to call this function again.
+     */
+    initialise(): Promise<void>;
+    /**
+     * Start the Postgres cluster with the given configuration. The cluster is
+     * started as a seperate process, unmanaged by NodeJS. It is automatically
+     * shut down when the script exits.
+     */
+    start(): Promise<void>;
+    /**
+     * Stop an already started cluster with the given configuration.
+     * NOTE: If you have `persisent` set to false, this method WILL DELETE your
+     * database files. You will need to call `.initialise()` again after executing
+     * this method.
+     */
+    stop(): Promise<void>;
+    /**
+     * Create a node-postgres client using the existing cluster configuration.
+     *
+     * @param database The database that the postgres client should connect to
+     * @param host The host that should be pre-filled in the connection options
+     * @returns Client
+     */
+    getPgClient(database?: string, host?: string): pg.Client;
+    /**
+     * Create a database with a given name on the cluster
+     */
+    createDatabase(name: string): Promise<void>;
+    /**
+     * Drop a database with a given name on the cluster
+     */
+    dropDatabase(name: string): Promise<void>;
+    /**
+     * Warn the user in case they're trying to run this library as a root user
+     */
+    private checkForRootUser;
+    /**
+     * Retrieve the uid and gid for a particular user
+     */
+    private getUidAndGid;
+}
+export default EmbeddedPostgres;