@seedcord/plugins 0.5.0 → 0.6.0

package/dist/index.d.mts

@@ -0,0 +1,1273 @@
+import mongoose, { Mongoose } from "mongoose";
+import { Core, Logger, Plugin, TypedConstructor } from "seedcord";
+import { Kysely, KyselyConfig } from "kysely";
+import { Pool, PoolConfig } from "pg";
+import { MigrationInfo, NoMigrations } from "kysely/migration";
+import { HmrUpdateEvent } from "@seedcord/cli";
+//#region src/mongo/types/MongoOptions.d.ts
+/**
+ * Configuration options for MongoDB connection and service loading.
+ */
+interface MongoOptions {
+  /** Directory path containing database service classes */
+  dir: string;
+  /** MongoDB connection URI */
+  uri: string;
+  /** Database name to use */
+  name: string;
+  /** mongoose connection options */
+  connectionOptions?: mongoose.ConnectOptions | undefined;
+  /** Plugin timeout in milliseconds */
+  timeout?: number;
+}
+//#endregion
+//#region src/mongo/types/MongoServices.d.ts
+/**
+ * Registry of available database services.
+ *
+ * This interface can be augmented via declaration merging to add
+ * type-safe service definitions when using the \@RegisterMongoService and \@RegisterMongoModel decorator.
+ *
+ * @example
+ * ```typescript
+ * declare module '@seedcord/plugins' {
+ *   interface MongoServices {
+ *     'user': Users;
+ *     'guild': Guilds;
+ *   }
+ * }
+ * ```
+ */
+interface MongoServices {}
+/**
+ * Helper type to extract service keys from the Services interface.
+ */
+type MongoServiceKeys = keyof MongoServices;
+//#endregion
+//#region src/mongo/Mongo.d.ts
+/**
+ * MongoDB integration plugin for Seedcord.
+ *
+ * Manages MongoDB connections, service loading, and provides type-safe
+ * access to database services through service registration decorators.
+ */
+declare class Mongo extends Plugin {
+  readonly core: Core;
+  private readonly options;
+  readonly logger: Logger;
+  private isInitialised;
+  private servicesReady;
+  private readonly uri;
+  private readonly _services;
+  /**
+   * Map of all loaded services. Keys come from `@RegisterMongoService('key')`.
+   *
+   * @throws A {@link SeedcordError} if accessed before the plugin finishes initializing (e.g. from
+   * a plugin that starts in an earlier phase).
+   */
+  get services(): MongoServices;
+  /** Exposed Mongoose instance once `init` completes. */
+  connection: Mongoose;
+  private readonly hmrHandler?;
+  constructor(core: Core, options: MongoOptions);
+  private getArtifacts;
+  /** @internal For use in dev mode */
+  onHmr(event: HmrUpdateEvent): Promise<void>;
+  init(): Promise<void>;
+  stop(): Promise<void>;
+  private connect;
+  private clearModels;
+  private disconnect;
+  private loadServices;
+  private initializeService;
+  private isServiceClass;
+  /**
+   * Register hook used by decorated services.
+   *
+   * @internal
+   */
+  _register(key: string, instance: unknown): void;
+  private unregister;
+}
+//#endregion
+//#region src/mongo/types/MongoDocument.d.ts
+/**
+ * Basic document interface with MongoDB ObjectId field.
+ *
+ * Represents the minimal structure of a MongoDB document
+ * with the required `_id` field.
+ */
+interface MongoDocument {
+  /** MongoDB document identifier */
+  _id: string;
+}
+//#endregion
+//#region src/mongo/MongoService.d.ts
+/**
+ * Base class for MongoDB service layers
+ *
+ * Provides typed access to MongoDB collections through Mongoose models.
+ * Services are automatically registered with the Mongo plugin when instantiated.
+ *
+ * @typeParam Doc - The document type this service manages
+ * @example
+ * ```typescript
+ * \@RegisterMongoService('users')
+ * export class Users extends MongoService<IUser> {
+ *   \@RegisterMongoModel('users')
+ *   public static schema = new mongoose.Schema<IUser>({
+ *     username: { type: String, required: true, unique: true }
+ *   });
+ *
+ *   // Custom methods here
+ *   public async findByUsername(username: string) {
+ *     return this.model.findOne({ username });
+ *   }
+ * }
+ * ```
+ */
+declare abstract class MongoService<Doc extends MongoDocument = MongoDocument> {
+  protected readonly db: Mongo;
+  protected readonly core: Core;
+  readonly model: mongoose.Model<Doc>;
+  constructor(db: Mongo, core: Core);
+}
+//#endregion
+//#region src/mongo/decorators/RegisterMongoModel.d.ts
+/**
+ * Associates a Mongoose model with a database service
+ *
+ * Creates a Mongoose model from the decorated static schema property and stores it
+ * for service registration. The model becomes available as `this.model` in the service.
+ * Must be applied to a `public static schema` property in the service class.
+ *
+ * @typeParam TService - The service key type
+ * @param collection - Collection name for the Mongoose model
+ * @decorator
+ * @example
+ * ```typescript
+ * \@RegisterMongoService('users')
+ * export class Users extends MongoService<IUser> {
+ *   \@RegisterMongoModel('users')
+ *   public static schema = new mongoose.Schema<IUser>({
+ *     username: { type: String, required: true, unique: true }
+ *   });
+ * }
+ * ```
+ */
+declare function RegisterMongoModel<TService extends MongoServiceKeys>(collection: TService): <SchemaObj extends Record<KeyOfSchema, mongoose.Schema>, KeyOfSchema extends keyof SchemaObj & (string | symbol)>(target: SchemaObj, propertyKey: KeyOfSchema) => void;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/primitive.d.ts
+/**
+Matches any [primitive value](https://developer.mozilla.org/en-US/docs/Glossary/Primitive).
+
+@category Type
+*/
+type Primitive = null | undefined | string | number | boolean | symbol | bigint;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/basic.d.ts
+/**
+Matches a [`class` constructor](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes).
+
+@category Class
+*/
+type Constructor<T, Arguments extends unknown[] = any[]> = new (...arguments_: Arguments) => T;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/is-any.d.ts
+/**
+Returns a boolean for whether the given type is `any`.
+
+@link https://stackoverflow.com/a/49928360/1490091
+
+Useful in type utilities, such as disallowing `any`s to be passed to a function.
+
+@example
+```
+import type {IsAny} from 'type-fest';
+
+const typedObject = {a: 1, b: 2} as const;
+const anyObject: any = {a: 1, b: 2};
+
+function get<O extends (IsAny<O> extends true ? {} : Record<string, number>), K extends keyof O = keyof O>(object: O, key: K) {
+	return object[key];
+}
+
+const typedA = get(typedObject, 'a');
+//=> 1
+
+const anyA = get(anyObject, 'a');
+//=> any
+```
+
+@category Type Guard
+@category Utilities
+*/
+type IsAny<T> = 0 extends 1 & NoInfer<T> ? true : false;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/is-optional-key-of.d.ts
+/**
+Returns a boolean for whether the given key is an optional key of type.
+
+This is useful when writing utility types or schema validators that need to differentiate `optional` keys.
+
+@example
+```
+import type {IsOptionalKeyOf} from 'type-fest';
+
+type User = {
+	name: string;
+	surname: string;
+
+	luckyNumber?: number;
+};
+
+type Admin = {
+	name: string;
+	surname?: string;
+};
+
+type T1 = IsOptionalKeyOf<User, 'luckyNumber'>;
+//=> true
+
+type T2 = IsOptionalKeyOf<User, 'name'>;
+//=> false
+
+type T3 = IsOptionalKeyOf<User, 'name' | 'luckyNumber'>;
+//=> boolean
+
+type T4 = IsOptionalKeyOf<User | Admin, 'name'>;
+//=> false
+
+type T5 = IsOptionalKeyOf<User | Admin, 'surname'>;
+//=> boolean
+```
+
+@category Type Guard
+@category Utilities
+*/
+type IsOptionalKeyOf<Type extends object, Key extends keyof Type> = IsAny<Type | Key> extends true ? never : Key extends keyof Type ? Type extends Record<Key, Type[Key]> ? false : true : false;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/optional-keys-of.d.ts
+/**
+Extract all optional keys from the given type.
+
+This is useful when you want to create a new type that contains different type values for the optional keys only.
+
+@example
+```
+import type {OptionalKeysOf, Except} from 'type-fest';
+
+type User = {
+	name: string;
+	surname: string;
+
+	luckyNumber?: number;
+};
+
+const REMOVE_FIELD = Symbol('remove field symbol');
+type UpdateOperation<Entity extends object> = Except<Partial<Entity>, OptionalKeysOf<Entity>> & {
+	[Key in OptionalKeysOf<Entity>]?: Entity[Key] | typeof REMOVE_FIELD;
+};
+
+const update1: UpdateOperation<User> = {
+	name: 'Alice',
+};
+
+const update2: UpdateOperation<User> = {
+	name: 'Bob',
+	luckyNumber: REMOVE_FIELD,
+};
+```
+
+@category Utilities
+*/
+type OptionalKeysOf<Type extends object> = Type extends unknown // For distributing `Type`
+? (keyof { [Key in keyof Type as IsOptionalKeyOf<Type, Key> extends false ? never : Key]: never }) & keyof Type // Intersect with `keyof Type` to ensure result of `OptionalKeysOf<Type>` is always assignable to `keyof Type`
+: never;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/required-keys-of.d.ts
+/**
+Extract all required keys from the given type.
+
+This is useful when you want to create a new type that contains different type values for the required keys only or use the list of keys for validation purposes, etc...
+
+@example
+```
+import type {RequiredKeysOf} from 'type-fest';
+
+declare function createValidation<
+	Entity extends object,
+	Key extends RequiredKeysOf<Entity> = RequiredKeysOf<Entity>,
+>(field: Key, validator: (value: Entity[Key]) => boolean): (entity: Entity) => boolean;
+
+type User = {
+	name: string;
+	surname: string;
+	luckyNumber?: number;
+};
+
+const validator1 = createValidation<User>('name', value => value.length < 25);
+const validator2 = createValidation<User>('surname', value => value.length < 25);
+
+// @ts-expect-error
+const validator3 = createValidation<User>('luckyNumber', value => value > 0);
+// Error: Argument of type '"luckyNumber"' is not assignable to parameter of type '"name" | "surname"'.
+```
+
+@category Utilities
+*/
+type RequiredKeysOf<Type extends object> = Type extends unknown // For distributing `Type`
+? Exclude<keyof Type, OptionalKeysOf<Type>> : never;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/is-never.d.ts
+/**
+Returns a boolean for whether the given type is `never`.
+
+@link https://github.com/microsoft/TypeScript/issues/31751#issuecomment-498526919
+@link https://stackoverflow.com/a/53984913/10292952
+@link https://www.zhenghao.io/posts/ts-never
+
+Useful in type utilities, such as checking if something does not occur.
+
+@example
+```
+import type {IsNever, And} from 'type-fest';
+
+type A = IsNever<never>;
+//=> true
+
+type B = IsNever<any>;
+//=> false
+
+type C = IsNever<unknown>;
+//=> false
+
+type D = IsNever<never[]>;
+//=> false
+
+type E = IsNever<object>;
+//=> false
+
+type F = IsNever<string>;
+//=> false
+```
+
+@example
+```
+import type {IsNever} from 'type-fest';
+
+type IsTrue<T> = T extends true ? true : false;
+
+// When a distributive conditional is instantiated with `never`, the entire conditional results in `never`.
+type A = IsTrue<never>;
+//=> never
+
+// If you don't want that behaviour, you can explicitly add an `IsNever` check before the distributive conditional.
+type IsTrueFixed<T> =
+	IsNever<T> extends true ? false : T extends true ? true : false;
+
+type B = IsTrueFixed<never>;
+//=> false
+```
+
+@category Type Guard
+@category Utilities
+*/
+type IsNever<T> = [T] extends [never] ? true : false;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/if.d.ts
+/**
+An if-else-like type that resolves depending on whether the given `boolean` type is `true` or `false`.
+
+Use-cases:
+- You can use this in combination with `Is*` types to create an if-else-like experience. For example, `If<IsAny<any>, 'is any', 'not any'>`.
+
+Note:
+- Returns a union of if branch and else branch if the given type is `boolean` or `any`. For example, `If<boolean, 'Y', 'N'>` will return `'Y' | 'N'`.
+- Returns the else branch if the given type is `never`. For example, `If<never, 'Y', 'N'>` will return `'N'`.
+
+@example
+```
+import type {If} from 'type-fest';
+
+type A = If<true, 'yes', 'no'>;
+//=> 'yes'
+
+type B = If<false, 'yes', 'no'>;
+//=> 'no'
+
+type C = If<boolean, 'yes', 'no'>;
+//=> 'yes' | 'no'
+
+type D = If<any, 'yes', 'no'>;
+//=> 'yes' | 'no'
+
+type E = If<never, 'yes', 'no'>;
+//=> 'no'
+```
+
+@example
+```
+import type {If, IsAny, IsNever} from 'type-fest';
+
+type A = If<IsAny<unknown>, 'is any', 'not any'>;
+//=> 'not any'
+
+type B = If<IsNever<never>, 'is never', 'not never'>;
+//=> 'is never'
+```
+
+@example
+```
+import type {If, IsEqual} from 'type-fest';
+
+type IfEqual<T, U, IfBranch, ElseBranch> = If<IsEqual<T, U>, IfBranch, ElseBranch>;
+
+type A = IfEqual<string, string, 'equal', 'not equal'>;
+//=> 'equal'
+
+type B = IfEqual<string, number, 'equal', 'not equal'>;
+//=> 'not equal'
+```
+
+Note: Sometimes using the `If` type can make an implementation non–tail-recursive, which can impact performance. In such cases, it’s better to use a conditional directly. Refer to the following example:
+
+@example
+```
+import type {If, IsEqual, StringRepeat} from 'type-fest';
+
+type HundredZeroes = StringRepeat<'0', 100>;
+
+// The following implementation is not tail recursive
+type Includes<S extends string, Char extends string> =
+	S extends `${infer First}${infer Rest}`
+		? If<IsEqual<First, Char>,
+			'found',
+			Includes<Rest, Char>>
+		: 'not found';
+
+// Hence, instantiations with long strings will fail
+// @ts-expect-error
+type Fails = Includes<HundredZeroes, '1'>;
+//           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+// Error: Type instantiation is excessively deep and possibly infinite.
+
+// However, if we use a simple conditional instead of `If`, the implementation becomes tail-recursive
+type IncludesWithoutIf<S extends string, Char extends string> =
+	S extends `${infer First}${infer Rest}`
+		? IsEqual<First, Char> extends true
+			? 'found'
+			: IncludesWithoutIf<Rest, Char>
+		: 'not found';
+
+// Now, instantiations with long strings will work
+type Works = IncludesWithoutIf<HundredZeroes, '1'>;
+//=> 'not found'
+```
+
+@category Type Guard
+@category Utilities
+*/
+type If<Type extends boolean, IfBranch, ElseBranch> = IsNever<Type> extends true ? ElseBranch : Type extends true ? IfBranch : ElseBranch;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/simplify.d.ts
+/**
+Useful to flatten the type output to improve type hints shown in editors. And also to transform an interface into a type to aide with assignability.
+
+@example
+```
+import type {Simplify} from 'type-fest';
+
+type PositionProps = {
+	top: number;
+	left: number;
+};
+
+type SizeProps = {
+	width: number;
+	height: number;
+};
+
+// In your editor, hovering over `Props` will show a flattened object with all the properties.
+type Props = Simplify<PositionProps & SizeProps>;
+```
+
+Sometimes it is desired to pass a value as a function argument that has a different type. At first inspection it may seem assignable, and then you discover it is not because the `value`'s type definition was defined as an interface. In the following example, `fn` requires an argument of type `Record<string, unknown>`. If the value is defined as a literal, then it is assignable. And if the `value` is defined as type using the `Simplify` utility the value is assignable.  But if the `value` is defined as an interface, it is not assignable because the interface is not sealed and elsewhere a non-string property could be added to the interface.
+
+If the type definition must be an interface (perhaps it was defined in a third-party npm package), then the `value` can be defined as `const value: Simplify<SomeInterface> = ...`. Then `value` will be assignable to the `fn` argument.  Or the `value` can be cast as `Simplify<SomeInterface>` if you can't re-declare the `value`.
+
+@example
+```
+import type {Simplify} from 'type-fest';
+
+interface SomeInterface {
+	foo: number;
+	bar?: string;
+	baz: number | undefined;
+}
+
+type SomeType = {
+	foo: number;
+	bar?: string;
+	baz: number | undefined;
+};
+
+const literal = {foo: 123, bar: 'hello', baz: 456};
+const someType: SomeType = literal;
+const someInterface: SomeInterface = literal;
+
+declare function fn(object: Record<string, unknown>): void;
+
+fn(literal); // Good: literal object type is sealed
+fn(someType); // Good: type is sealed
+// @ts-expect-error
+fn(someInterface); // Error: Index signature for type 'string' is missing in type 'someInterface'. Because `interface` can be re-opened
+fn(someInterface as Simplify<SomeInterface>); // Good: transform an `interface` into a `type`
+```
+
+@link https://github.com/microsoft/TypeScript/issues/15300
+@see {@link SimplifyDeep}
+@category Object
+*/
+type Simplify<T> = { [KeyType in keyof T]: T[KeyType] } & {};
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/is-equal.d.ts
+/**
+Returns a boolean for whether the two given types are equal.
+
+@link https://github.com/microsoft/TypeScript/issues/27024#issuecomment-421529650
+@link https://stackoverflow.com/questions/68961864/how-does-the-equals-work-in-typescript/68963796#68963796
+
+Use-cases:
+- If you want to make a conditional branch based on the result of a comparison of two types.
+
+@example
+```
+import type {IsEqual} from 'type-fest';
+
+// This type returns a boolean for whether the given array includes the given item.
+// `IsEqual` is used to compare the given array at position 0 and the given item and then return true if they are equal.
+type Includes<Value extends readonly any[], Item> =
+	Value extends readonly [Value[0], ...infer rest]
+		? IsEqual<Value[0], Item> extends true
+			? true
+			: Includes<rest, Item>
+		: false;
+```
+
+@category Type Guard
+@category Utilities
+*/
+type IsEqual<A, B> = [A] extends [B] ? [B] extends [A] ? _IsEqual<A, B> : false : false;
+// This version fails the `equalWrappedTupleIntersectionToBeNeverAndNeverExpanded` test in `test-d/is-equal.ts`.
+type _IsEqual<A, B> = (<G>() => G extends A & G | G ? 1 : 2) extends (<G>() => G extends B & G | G ? 1 : 2) ? true : false;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/omit-index-signature.d.ts
+/**
+Omit any index signatures from the given object type, leaving only explicitly defined properties.
+
+This is the counterpart of `PickIndexSignature`.
+
+Use-cases:
+- Remove overly permissive signatures from third-party types.
+
+This type was taken from this [StackOverflow answer](https://stackoverflow.com/a/68261113/420747).
+
+It relies on the fact that an empty object (`{}`) is assignable to an object with just an index signature, like `Record<string, unknown>`, but not to an object with explicitly defined keys, like `Record<'foo' | 'bar', unknown>`.
+
+(The actual value type, `unknown`, is irrelevant and could be any type. Only the key type matters.)
+
+```
+const indexed: Record<string, unknown> = {}; // Allowed
+
+// @ts-expect-error
+const keyed: Record<'foo', unknown> = {}; // Error
+// TS2739: Type '{}' is missing the following properties from type 'Record<"foo" | "bar", unknown>': foo, bar
+```
+
+Instead of causing a type error like the above, you can also use a [conditional type](https://www.typescriptlang.org/docs/handbook/2/conditional-types.html) to test whether a type is assignable to another:
+
+```
+type Indexed = {} extends Record<string, unknown>
+	? '✅ `{}` is assignable to `Record<string, unknown>`'
+	: '❌ `{}` is NOT assignable to `Record<string, unknown>`';
+
+type IndexedResult = Indexed;
+//=> '✅ `{}` is assignable to `Record<string, unknown>`'
+
+type Keyed = {} extends Record<'foo' | 'bar', unknown>
+	? '✅ `{}` is assignable to `Record<\'foo\' | \'bar\', unknown>`'
+	: '❌ `{}` is NOT assignable to `Record<\'foo\' | \'bar\', unknown>`';
+
+type KeyedResult = Keyed;
+//=> '❌ `{}` is NOT assignable to `Record<\'foo\' | \'bar\', unknown>`'
+```
+
+Using a [mapped type](https://www.typescriptlang.org/docs/handbook/2/mapped-types.html#further-exploration), you can then check for each `KeyType` of `ObjectType`...
+
+```
+type OmitIndexSignature<ObjectType> = {
+	[KeyType in keyof ObjectType // Map each key of `ObjectType`...
+	]: ObjectType[KeyType]; // ...to its original value, i.e. `OmitIndexSignature<Foo> == Foo`.
+};
+```
+
+...whether an empty object (`{}`) would be assignable to an object with that `KeyType` (`Record<KeyType, unknown>`)...
+
+```
+type OmitIndexSignature<ObjectType> = {
+	[KeyType in keyof ObjectType
+	// Is `{}` assignable to `Record<KeyType, unknown>`?
+	as {} extends Record<KeyType, unknown>
+		? never // ✅ `{}` is assignable to `Record<KeyType, unknown>`
+		: KeyType // ❌ `{}` is NOT assignable to `Record<KeyType, unknown>`
+	]: ObjectType[KeyType];
+};
+```
+
+If `{}` is assignable, it means that `KeyType` is an index signature and we want to remove it. If it is not assignable, `KeyType` is a "real" key and we want to keep it.
+
+@example
+```
+import type {OmitIndexSignature} from 'type-fest';
+
+type Example = {
+	// These index signatures will be removed.
+	[x: string]: any;
+	[x: number]: any;
+	[x: symbol]: any;
+	[x: `head-${string}`]: string;
+	[x: `${string}-tail`]: string;
+	[x: `head-${string}-tail`]: string;
+	[x: `${bigint}`]: string;
+	[x: `embedded-${number}`]: string;
+
+	// These explicitly defined keys will remain.
+	foo: 'bar';
+	qux?: 'baz';
+};
+
+type ExampleWithoutIndexSignatures = OmitIndexSignature<Example>;
+//=> {foo: 'bar'; qux?: 'baz'}
+```
+
+@see {@link PickIndexSignature}
+@category Object
+*/
+type OmitIndexSignature<ObjectType> = { [KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? never : KeyType]: ObjectType[KeyType] };
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/pick-index-signature.d.ts
+/**
+Pick only index signatures from the given object type, leaving out all explicitly defined properties.
+
+This is the counterpart of `OmitIndexSignature`.
+
+@example
+```
+import type {PickIndexSignature} from 'type-fest';
+
+declare const symbolKey: unique symbol;
+
+type Example = {
+	// These index signatures will remain.
+	[x: string]: unknown;
+	[x: number]: unknown;
+	[x: symbol]: unknown;
+	[x: `head-${string}`]: string;
+	[x: `${string}-tail`]: string;
+	[x: `head-${string}-tail`]: string;
+	[x: `${bigint}`]: string;
+	[x: `embedded-${number}`]: string;
+
+	// These explicitly defined keys will be removed.
+	['kebab-case-key']: string;
+	[symbolKey]: string;
+	foo: 'bar';
+	qux?: 'baz';
+};
+
+type ExampleIndexSignature = PickIndexSignature<Example>;
+// {
+// 	[x: string]: unknown;
+// 	[x: number]: unknown;
+// 	[x: symbol]: unknown;
+// 	[x: `head-${string}`]: string;
+// 	[x: `${string}-tail`]: string;
+// 	[x: `head-${string}-tail`]: string;
+// 	[x: `${bigint}`]: string;
+// 	[x: `embedded-${number}`]: string;
+// }
+```
+
+@see {@link OmitIndexSignature}
+@category Object
+*/
+type PickIndexSignature<ObjectType> = { [KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? KeyType : never]: ObjectType[KeyType] };
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/merge.d.ts
+// Merges two objects without worrying about index signatures.
+type SimpleMerge<Destination, Source> = Simplify<{ [Key in keyof Destination as Key extends keyof Source ? never : Key]: Destination[Key] } & Source>;
+/**
+Merge two types into a new type. Keys of the second type overrides keys of the first type.
+
+This is different from the TypeScript `&` (intersection) operator. With `&`, conflicting property types are intersected, which often results in `never`. For example, `{a: string} & {a: number}` makes `a` become `string & number`, which resolves to `never`. With `Merge`, the second type's keys cleanly override the first, so `Merge<{a: string}, {a: number}>` gives `{a: number}` as expected. `Merge` also produces a flattened type (via `Simplify`), making it more readable in IDE tooltips compared to `A & B`.
+
+@example
+```
+import type {Merge} from 'type-fest';
+
+type Foo = {
+	a: string;
+	b: number;
+};
+
+type Bar = {
+	a: number; // Conflicts with Foo['a']
+	c: boolean;
+};
+
+// With `&`, `a` becomes `string & number` which is `never`. Not what you want.
+type WithIntersection = (Foo & Bar)['a'];
+//=> never
+
+// With `Merge`, `a` is cleanly overridden to `number`.
+type WithMerge = Merge<Foo, Bar>['a'];
+//=> number
+```
+
+@example
+```
+import type {Merge} from 'type-fest';
+
+type Foo = {
+	[x: string]: unknown;
+	[x: number]: unknown;
+	foo: string;
+	bar: symbol;
+};
+
+type Bar = {
+	[x: number]: number;
+	[x: symbol]: unknown;
+	bar: Date;
+	baz: boolean;
+};
+
+export type FooBar = Merge<Foo, Bar>;
+//=> {
+// 	[x: string]: unknown;
+// 	[x: number]: number;
+// 	[x: symbol]: unknown;
+// 	foo: string;
+// 	bar: Date;
+// 	baz: boolean;
+// }
+```
+
+Note: If you want a merge type that more accurately reflects the runtime behavior of object spread or `Object.assign`, refer to the {@link ObjectMerge} type.
+
+@see {@link ObjectMerge}
+@category Object
+*/
+type Merge<Destination, Source> = Destination extends unknown // For distributing `Destination`
+? Source extends unknown // For distributing `Source`
+? If<IsEqual<Destination, Source>, Destination, _Merge<Destination, Source>> : never // Should never happen
+: never;
+// Should never happen
+type _Merge<Destination, Source> = Simplify<SimpleMerge<PickIndexSignature<Destination>, PickIndexSignature<Source>> & SimpleMerge<OmitIndexSignature<Destination>, OmitIndexSignature<Source>>>;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/internal/object.d.ts
+/**
+Merges user specified options with default options.
+
+@example
+```
+type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
+type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: false};
+type SpecifiedOptions = {leavesOnly: true};
+
+type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
+//=> {maxRecursionDepth: 10; leavesOnly: true}
+```
+
+@example
+```
+// Complains if default values are not provided for optional options
+
+type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
+type DefaultPathsOptions = {maxRecursionDepth: 10};
+type SpecifiedOptions = {};
+
+type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
+//                                              ~~~~~~~~~~~~~~~~~~~
+// Property 'leavesOnly' is missing in type 'DefaultPathsOptions' but required in type '{ maxRecursionDepth: number; leavesOnly: boolean; }'.
+```
+
+@example
+```
+// Complains if an option's default type does not conform to the expected type
+
+type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
+type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: 'no'};
+type SpecifiedOptions = {};
+
+type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
+//                                              ~~~~~~~~~~~~~~~~~~~
+// Types of property 'leavesOnly' are incompatible. Type 'string' is not assignable to type 'boolean'.
+```
+
+@example
+```
+// Complains if an option's specified type does not conform to the expected type
+
+type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
+type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: false};
+type SpecifiedOptions = {leavesOnly: 'yes'};
+
+type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
+//                                                                   ~~~~~~~~~~~~~~~~
+// Types of property 'leavesOnly' are incompatible. Type 'string' is not assignable to type 'boolean'.
+```
+*/
+type ApplyDefaultOptions<Options extends object, Defaults extends Simplify<Omit<Required<Options>, RequiredKeysOf<Options>> & Partial<Record<RequiredKeysOf<Options>, never>>>, SpecifiedOptions extends Options> = If<IsAny<SpecifiedOptions>, Defaults, If<IsNever<SpecifiedOptions>, Defaults, Simplify<Merge<Defaults, { [Key in keyof SpecifiedOptions as Key extends OptionalKeysOf<Options> ? undefined extends SpecifiedOptions[Key] ? never : Key : Key]: SpecifiedOptions[Key] }> & Required<Options>>>>;
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/except.d.ts
+/**
+Filter out keys from an object.
+
+Returns `never` if `Exclude` is strictly equal to `Key`.
+Returns `never` if `Key` extends `Exclude`.
+Returns `Key` otherwise.
+
+@example
+```
+type Filtered = Filter<'foo', 'foo'>;
+//=> never
+```
+
+@example
+```
+type Filtered = Filter<'bar', string>;
+//=> never
+```
+
+@example
+```
+type Filtered = Filter<'bar', 'foo'>;
+//=> 'bar'
+```
+
+@see {Except}
+*/
+type Filter<KeyType, ExcludeType> = IsEqual<KeyType, ExcludeType> extends true ? never : (KeyType extends ExcludeType ? never : KeyType);
+type ExceptOptions = {
+  /**
+  Disallow assigning non-specified properties.
+  	Note that any omitted properties in the resulting type will be present in autocomplete as `undefined`.
+  	@default false
+  */
+  requireExactProps?: boolean;
+};
+type DefaultExceptOptions = {
+  requireExactProps: false;
+};
+/**
+Create a type from an object type without certain keys.
+
+We recommend setting the `requireExactProps` option to `true`.
+
+This type is a stricter version of [`Omit`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-5.html#the-omit-helper-type). The `Omit` type does not restrict the omitted keys to be keys present on the given type, while `Except` does. The benefits of a stricter type are avoiding typos and allowing the compiler to pick up on rename refactors automatically.
+
+This type was proposed to the TypeScript team, which declined it, saying they prefer that libraries implement stricter versions of the built-in types ([microsoft/TypeScript#30825](https://github.com/microsoft/TypeScript/issues/30825#issuecomment-523668235)).
+
+@example
+```
+import type {Except} from 'type-fest';
+
+type Foo = {
+	a: number;
+	b: string;
+};
+
+type FooWithoutA = Except<Foo, 'a'>;
+//=> {b: string}
+
+// @ts-expect-error
+const fooWithoutA: FooWithoutA = {a: 1, b: '2'};
+// errors: 'a' does not exist in type '{ b: string; }'
+
+type FooWithoutB = Except<Foo, 'b', {requireExactProps: true}>;
+//=> {a: number} & Partial<Record<'b', never>>
+
+// @ts-expect-error
+const fooWithoutB: FooWithoutB = {a: 1, b: '2'};
+// errors at 'b': Type 'string' is not assignable to type 'undefined'.
+
+// The `Omit` utility type doesn't work when omitting specific keys from objects containing index signatures.
+
+// Consider the following example:
+
+type UserData = {
+	[metadata: string]: string;
+	email: string;
+	name: string;
+	role: 'admin' | 'user';
+};
+
+// `Omit` clearly doesn't behave as expected in this case:
+type PostPayload = Omit<UserData, 'email'>;
+//=> {[x: string]: string; [x: number]: string}
+
+// In situations like this, `Except` works better.
+// It simply removes the `email` key while preserving all the other keys.
+type PostPayloadFixed = Except<UserData, 'email'>;
+//=> {[x: string]: string; name: string; role: 'admin' | 'user'}
+```
+
+@category Object
+*/
+type Except<ObjectType, KeysType extends keyof ObjectType, Options extends ExceptOptions = {}> = _Except<ObjectType, KeysType, ApplyDefaultOptions<ExceptOptions, DefaultExceptOptions, Options>>;
+type _Except<ObjectType, KeysType extends keyof ObjectType, Options extends Required<ExceptOptions>> = { [KeyType in keyof ObjectType as Filter<KeyType, KeysType>]: ObjectType[KeyType] } & (Options['requireExactProps'] extends true ? Partial<Record<KeysType, never>> : {});
+//#endregion
+//#region ../../node_modules/.pnpm/type-fest@5.6.0/node_modules/type-fest/source/literal-union.d.ts
+/**
+Create a union type by combining primitive types and literal types without sacrificing auto-completion in IDEs for the literal type part of the union.
+
+Currently, when a union type of a primitive type is combined with literal types, TypeScript loses all information about the combined literals. Thus, when such type is used in an IDE with autocompletion, no suggestions are made for the declared literals.
+
+This type is a workaround for [Microsoft/TypeScript#29729](https://github.com/Microsoft/TypeScript/issues/29729). It will be removed as soon as it's not needed anymore.
+
+@example
+```
+import type {LiteralUnion} from 'type-fest';
+
+// Before
+
+type Pet = 'dog' | 'cat' | string;
+
+const petWithoutAutocomplete: Pet = '';
+// Start typing in your TypeScript-enabled IDE.
+// You **will not** get auto-completion for `dog` and `cat` literals.
+
+// After
+
+type Pet2 = LiteralUnion<'dog' | 'cat', string>;
+
+const petWithAutoComplete: Pet2 = '';
+// You **will** get auto-completion for `dog` and `cat` literals.
+```
+
+@category Type
+*/
+type LiteralUnion<LiteralType, BaseType extends Primitive> = LiteralType | (BaseType & Record<never, never>);
+//#endregion
+//#region src/mongo/decorators/RegisterMongoService.d.ts
+/**
+ * Registers a database service with a typed key
+ *
+ * Associates a service class with a key for dependency injection.
+ * The service becomes available via `core.db.services[key]`.
+ *
+ * @typeParam TService - The service key type
+ * @param key - Service key for registration and type-safe access
+ * @decorator
+ * @example
+ * ```typescript
+ * \@RegisterMongoService('users')
+ * export class Users<Doc extends IUser = IUser> extends MongoService<Doc> {
+ *   // Some code
+ * }
+ * ```
+ */
+declare function RegisterMongoService<TService extends MongoServiceKeys>(key: TService): <DatabaseCtor extends Constructor<unknown> & {
+  prototype: MongoService;
+}>(ctor: DatabaseCtor) => void;
+//#endregion
+//#region src/kysely-pg/types/KpgOptions.d.ts
+/**
+ * Options that describe where migrations live and how the migrator should
+ * behave.
+ */
+interface KpgMigrationsOptions {
+  /** Directory path, single file path, or array of migration files */
+  readonly path: string | string[];
+  /** Allow running migrations even if new ones are inserted out of order */
+  readonly allowUnorderedMigrations?: boolean;
+  /** Custom table name used to track executed migrations */
+  readonly migrationTableName?: string;
+  /** Custom lock table name used by the migrator */
+  readonly migrationLockTableName?: string;
+  /** Schema that contains the migration bookkeeping tables */
+  readonly migrationTableSchema?: string;
+  /** Comparator that determines execution order for migrations */
+  readonly nameComparator?: (nameA: string, nameB: string) => number;
+  /** Behavior when the plugin connects. `true`/`undefined` runs to latest. */
+  readonly onStartup?: boolean | MigrationOptions;
+}
+/**
+ * Configuration options for Postgres connection and service discovery.
+ */
+interface KpgOptions {
+  /** Directory containing service classes. Make sure file(s)/folder(s) are built to `.js` in dist and aren't merged into a single file. */
+  readonly dir: string;
+  /** Migration settings */
+  readonly migrations: KpgMigrationsOptions;
+  /** Optional existing Pool instance or configuration overrides */
+  readonly pool?: Pool | PoolConfig;
+  /** Optional connection string used when a pool config is provided */
+  readonly connectionString?: string;
+  /** Optional SQL statements executed for each new connection */
+  readonly onConnectSQL?: string[];
+  /** Force using insecure SSL*/
+  readonly forceInsecureSSL?: boolean;
+  /** Kysely config (excludes dialect because it's Postgres for this plugin) */
+  readonly kysely?: Except<KyselyConfig, 'dialect'>;
+  /** Plugin timeout in milliseconds */
+  timeout?: number;
+}
+//#endregion
+//#region src/kysely-pg/types/KpgMigration.d.ts
+/**
+ * Target migration identifier used to indicate no migrations should be run. Uses Kysely's built-in `NO_MIGRATIONS` constant.
+ */
+type MigrationTarget = string | NoMigrations;
+/**
+ * Behavior configuration for migrations that should run automatically when a
+ * database connection is established.
+ */
+interface MigrationOptions {
+  /** Optional target migration to reach. Defaults to latest if omitted. */
+  readonly target?: MigrationTarget;
+  /** Direction to move along the migration timeline. Defaults to `latest`. */
+  readonly direction?: 'latest' | 'up' | 'down';
+  /** Number of steps to apply when direction is `up` or `down`. */
+  readonly steps?: number;
+}
+/**
+ * Behavior configuration for step-based migrations.
+ */
+interface StepMigrationOptions {
+  /** Number of steps to apply when direction is `up` or `down`. */
+  readonly steps?: number | undefined;
+}
+//#endregion
+//#region src/kysely-pg/types/KpgServices.d.ts
+/**
+ * Namespace interface that gets augmented by individual service packages.
+ *
+ * This interface can be augmented via declaration merging to add
+ * type-safe service definitions when using the `@RegisterKpgService` decorator.
+ *
+ * @example
+ * ```typescript
+ * declare module '@seedcord/plugins' {
+ *   interface KpgServices {
+ *     'users': Users;
+ *   }
+ * }
+ * ```
+ */
+interface KpgServices {}
+/**
+ * Union of all registered service keys.
+ *
+ * @internal
+ */
+type KpgServiceKeys = keyof KpgServices;
+//#endregion
+//#region src/kysely-pg/KyselyPg.d.ts
+/**
+ * Postgres plugin using Kysely.
+ *
+ * Handles setting up the connection pool, applying migrations, and
+ * registering decorated services so they can be resolved from the core.
+ */
+declare class KyselyPg<Database extends object> extends Plugin {
+  readonly core: Core;
+  private readonly options;
+  readonly logger: Logger;
+  private isInitialised;
+  private servicesReady;
+  /** Exposed Kysely instance once `init` completes. */
+  connection: Kysely<Database>;
+  private pool;
+  private onConnectHandler;
+  private migrationManager;
+  private readonly serviceRegistry;
+  private readonly databaseBootstrapper;
+  private databaseName;
+  private readonly hmrHandler?;
+  /**
+   * Map of all services registered with the plugin, keyed by their decorator name.
+   */
+  get services(): KpgServices;
+  constructor(core: Core, options: KpgOptions);
+  private getArtifacts;
+  /** @internal For use in dev mode */
+  onHmr(event: HmrUpdateEvent): Promise<void>;
+  /**
+   * Connects to Postgres, runs any startup migrations, and loads decorated services.
+   *
+   * Safe to call multiple times; subsequent calls exit early.
+   */
+  init(): Promise<void>;
+  /**
+   * Tears down the connection pool and clears the migration manager reference.
+   */
+  stop(): Promise<void>;
+  private connect;
+  private disconnect;
+  /**
+   * Runs migrations using the supplied options or defaults to `latest`.
+   *
+   * @param options - Target migration or direction overrides
+   */
+  migrate(options?: MigrationOptions): Promise<void>;
+  /**
+   * Runs a single upwards migration step unless a custom count is provided.
+   *
+   * @param options - Optional configuration for step-based execution
+   */
+  migrateUp(options?: StepMigrationOptions): Promise<void>;
+  /**
+   * Runs a single downwards migration step unless a custom count is provided.
+   *
+   * @param options - Optional configuration for step-based execution
+   */
+  migrateDown(options?: StepMigrationOptions): Promise<void>;
+  /**
+   * Lists every migration registered with the manager along with its execution state.
+   */
+  listMigrations(): Promise<readonly MigrationInfo[]>;
+  /**
+   * Lists unapplied migrations.
+   */
+  listPendingMigrations(): Promise<MigrationInfo[]>;
+  private getMigrationManager;
+  /**
+   * Register hook used by decorated services.
+   *
+   * @internal
+   */
+  _register(key: string, instance: unknown): void;
+  /**
+   * Tracks a service file with the HMR handler so dev reloads can swap it. No-op outside dev.
+   *
+   * @internal Lets {@link KpgServiceRegistry} reach the dev-only HMR handler without poking a
+   * private field.
+   */
+  trackServiceFile(filePath: string, ctor: KyselyServiceConstructor<Database>): void;
+  private resolvePool;
+  private createPoolConfig;
+  private registerOnConnectStatements;
+  private testPoolConnection;
+}
+//#endregion
+//#region src/kysely-pg/KpgService.d.ts
+/**
+ * Base class for KyselyPg services.
+ *
+ * Provides a small, typed shim around the shared Kysely instance and ensures
+ * that subclasses have been decorated with `@RegisterKpgService`.
+ *
+ * @typeParam Database - The database shape used by Kysely (tables as keys).
+ * @typeParam TTable - The specific table key from `Database` this service works with.
+ *
+ * @example
+ * ```typescript
+ * \@RegisterKpgService('users')
+ * export class UsersService extends KpgService<ImportedDatabaseInterface, 'users'> {
+ *   public async findById(id: string) {
+ *     return this.entity
+ *       .selectFrom(this.table)
+ *       .selectAll().where('id', '=', id)
+ *       .executeTakeFirst();
+ *   }
+ * }
+ *
+ * // Usage inside handlers:
+ * const user = await this.core.db.services.users.findById('abc');
+ * ```
+ */
+declare abstract class KpgService<Database extends object, TTable extends LiteralUnion<keyof Database, string>> {
+  protected readonly kysely: KyselyPg<Database>;
+  protected readonly core: Core;
+  readonly table: TTable;
+  constructor(kysely: KyselyPg<Database>, core: Core);
+  /**
+   * Shared Kysely instance used to interact with the Postgres database.
+   */
+  get db(): Kysely<Database>;
+}
+/** Constructor type for {@link KpgService} classes */
+type KyselyServiceConstructor<Database extends object = object> = TypedConstructor<typeof KpgService<Database, keyof Database & string>>;
+//#endregion
+//#region src/kysely-pg/types/KpgServiceRegistrationOptions.d.ts
+/**
+ * Extra configuration supplied to `@RegisterKpgService`.
+ */
+interface KpgServiceRegistrationOptions {
+  /**
+   * Optional override for the table name exposed via the service. Defaults to the provided key.
+   *
+   * You should set this if your table name does not match the service key.
+   */
+  table?: string;
+}
+//#endregion
+//#region src/kysely-pg/decorators/RegisterKpgService.d.ts
+/**
+ *
+ * Registers a Kysely PG service with the specified key and options.
+ *
+ * Associates a service class with a key for dependency injection.
+ * The service becomes available via `core.db.services[key]`.
+ *
+ * @typeParam TKey - The service key type
+ * @param key - Service key for registration and type-safe access
+ * @param options - Additional registration options
+ * @decorator
+ * @example
+ * ```typescript
+ * \@RegisterKpgService('users', { table: 'app_users' })
+ * export class UsersService extends KpgService<{ users: IUser }, 'users'> {
+ *   // Some code
+ * }
+ * ```
+ *
+ * @see {@link KpgService}
+ */
+declare function RegisterKpgService<TKey extends KpgServiceKeys>(key: TKey, options?: KpgServiceRegistrationOptions): <Ctor extends Constructor<KpgServices[TKey]>>(ctor: Ctor) => void;
+//#endregion
+//#region src/shared/WrapDatabaseError.d.ts
+/**
+ * Catches and wraps database operation errors.
+ *
+ * Wraps non-CustomError exceptions in DatabaseError instances
+ * with UUID tracking. Should be applied to database service methods.
+ *
+ * @typeParam TypeReturn - The return type of the decorated method
+ * @param errorMessage - Message to include when wrapping errors
+ * @decorator
+ * @example
+ * ```typescript
+ * class UserService extends MongoService<IUser> {
+ *   \@WrapDatabaseError('Failed to find user')
+ *   async findById(id: string) {
+ *     return this.model.findById(id);
+ *   }
+ * }
+ * ```
+ *
+ * @see {@link DatabaseError}
+ * @see {@link CustomError}
+ * @see {@link MongoService}
+ */
+declare function WrapDatabaseError<TypeReturn>(errorMessage: string): (_target: unknown, _propertyKey: string, descriptor: TypedPropertyDescriptor<(...args: any[]) => Promise<TypeReturn>>) => void;
+//#endregion
+//#region src/index.d.ts
+/** Package version */
+declare const version: string;
+//#endregion
+export { type KpgMigrationsOptions, type KpgOptions, KpgService, type KpgServiceRegistrationOptions, type KpgServices, KyselyPg, type MigrationOptions, type MigrationTarget, Mongo, type MongoDocument, MongoService, type MongoServices, RegisterKpgService, RegisterMongoModel, RegisterMongoService, type StepMigrationOptions, WrapDatabaseError, version };
+//# sourceMappingURL=index.d.mts.map