@frigear-nu/module-kit 0.0.5 → 0.0.6

package/README.md

@@ -116,6 +116,38 @@ call with the merged columns and deduplicated imports. The base `schema` file mu
 `sqliteTable('users', { ... })`) matching `name`, since it determines which factory (`sqliteTable`/`pgTable`/etc.) and
 SQL table name to use for the merged result.
 
+`name` also accepts an array, so a single `file` can export extension columns for several tables in one go, the same
+way `registerDatabaseTable` does:
+
+```ts
+extendDatabaseTable(nuxt, {
+  name: ['users', 'userPasskeys'],
+  resolver: createResolver(import.meta.url),
+  file: dialect => `./runtime/db/extra.${dialect}`,
+})
+```
+
+```ts
+// runtime/db/extra.sqlite.ts
+export const users = sqliteTable('users', {
+  locale: text().default('da'),
+})
+export const userPasskeys = sqliteTable('user_passkeys', {
+  label: text(),
+})
+```
+
+`name` can also be omitted entirely, in which case `file` is registered against every table that generates a schema -
+whichever table(s) it actually has a matching export for pick up its columns, exactly as the shared Nuxt-layer
+`server/db/extend.<dialect>.ts` files already do; tables with no matching export in `file` are left untouched:
+
+```ts
+extendDatabaseTable(nuxt, {
+  resolver: createResolver(import.meta.url),
+  file: dialect => `./runtime/db/extra.${dialect}`,
+})
+```
+
 #### Using a `factory`
 
 Pass `factory` to `registerDatabaseTable` when you need shared defaults (e.g. timestamps) applied consistently across

package/dist/module.json

@@ -4,7 +4,7 @@
   "compatibility": {
     "nuxt": ">=4.0.0"
   },
-  "version": "0.0.5",
+  "version": "0.0.6",
   "builder": {
     "@nuxt/module-builder": "1.0.3",
     "unbuild": "unknown"

package/dist/runtime/utils/server.d.ts

@@ -66,7 +66,16 @@ type DatabaseTableOptions = {
     extensionFile?: (dialect: string) => string;
 };
 type TableExtensionOptions = {
-    name: string;
+    /**
+     * The name of the table to extend (e.g. `users`). Pass an array of names (e.g. `['users', 'userPasskeys']`) when
+     * `file` exports columns for several tables at once - it's resolved and parsed once per matching table, same as
+     * if `extendDatabaseTable` had been called separately for each name with the same `file`.
+     *
+     * When omitted, `file` is registered against every table - whichever table(s) it actually has a matching export
+     * for (parsed the same way as the shared Nuxt-layer `server/db/extend.<dialect>.ts` files) pick up its columns;
+     * tables it has no matching export for are unaffected.
+     */
+    name?: string | string[];
     resolver: ReturnType<typeof createResolver>;
     file: (dialect: string) => string;
 };

package/dist/runtime/utils/server.js

@@ -13,8 +13,9 @@ export const onDatabaseSchemaExtend = async (nuxt, extender) => {
   return nuxt.hook("hub:db:schema:extend", extender);
 };
 export const extendDatabaseTable = (nuxt, options) => {
+  const names = options.name === void 0 ? void 0 : Array.isArray(options.name) ? options.name : [options.name];
   nuxt.hook("module-kit:db:table:extend", async ({ name, dialect, paths }) => {
-    if (name === options.name) {
+    if (names === void 0 || names.includes(name)) {
       const file = await options.resolver.resolvePath(options.file(dialect));
       if (existsSync(file)) paths.push(file);
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@frigear-nu/module-kit",
-  "version": "0.0.5",
+  "version": "0.0.6",
   "type": "module",
   "private": false,
   "description": "Frigear Module Kit",