@beignet/provider-db-drizzle 0.0.26 → 0.0.28

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @beignet/provider-db-drizzle
 
+## 0.0.28
+
+## 0.0.27
+
+### Patch Changes
+
+- f2461a9: Add lazy Next route server loaders and update generated route files and package docs to avoid booting providers during production build imports.
+
 ## 0.0.26
 
 ### Patch Changes

package/README.md

@@ -174,16 +174,19 @@ export type AppPorts = {
 
 ```ts
 // server/index.ts
-import { createNextServer } from "@beignet/next";
+import { createNextServer, createNextServerLoader } from "@beignet/next";
 import { appPorts } from "@/infra/app-ports";
 import { routes } from "@/server/routes";
-import { providers } from "./providers";
 
-export const server = await createNextServer({
-  ports: appPorts,
-  providers,
-  context: ({ ports }) => ({ ports }),
-  routes,
+export const getServer = createNextServerLoader(async () => {
+  const { providers } = await import("./providers");
+
+  return createNextServer({
+    ports: appPorts,
+    providers,
+    context: ({ ports }) => ({ ports }),
+    routes,
+  });
 });
 ```
 
@@ -962,15 +965,14 @@ These choices are deliberate and shared across the three backends:
   idempotency timestamps, plus audit `occurred_at`, as ISO-8601 UTC strings in
   text columns. This keeps retry timing, lease expiry, replay semantics, and
   audit ordering identical across backends, and lexicographic ordering matches
-  chronological ordering. A later release may move the Postgres ports to
-  `timestamptz`.
+  chronological ordering.
 - **MySQL key length limits.** SQLite and Postgres use unbounded text columns
   for idempotency keys; MySQL needs bounded `varchar` columns for its unique
   index, so over-length keys fail loudly rather than truncating silently.
 - **Shared conformance suite.** One conformance suite runs the same Unit of
   Work, outbox, and idempotency behavior tests against SQLite (libSQL),
-  Postgres (PGlite in-process plus a real server in CI), and MySQL (a real
-  server in CI), so durable workflow semantics do not drift between backends.
+  Postgres, and MySQL, so durable workflow semantics do not drift between
+  backends.
 
 ## Advanced usage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beignet/provider-db-drizzle",
-  "version": "0.0.26",
+  "version": "0.0.28",
   "type": "module",
   "description": "Drizzle ORM database providers for Beignet — typed DbPort, unit of work, audit logs, outbox, and idempotency for SQLite (libSQL/Turso), Postgres, and MySQL.",
   "exports": {