@squadbase/vite-server 0.1.17 → 0.1.19-dev.2880e8d

package/build-entry/server-entry.mjs

@@ -0,0 +1,23 @@
+// Server entry used by squadbasePlugin for both the dev server and the build.
+//
+// It imports the app and the server-logic files collected by `import.meta.glob`
+// (via the `virtual:squadbase-server-logics` module), populates the registry,
+// and re-exports the app as default. Because the handlers are collected through
+// the same Vite module graph as the server, hono's context storage resolves to a
+// single instance and `getContext` works.
+//
+// Population goes through `@squadbase/vite-server/main` (not `.`) so it targets the
+// same module instance as the running app.
+import { serve } from "@hono/node-server";
+import app, { populateServerLogics } from "@squadbase/vite-server/main";
+import { handlerModules, metaModules } from "virtual:squadbase-server-logics";
+
+populateServerLogics({ handlerModules, metaModules });
+
+// In the built (production) server, start the Node HTTP server. In dev the app is
+// served by @hono/vite-dev-server via `app.fetch`, so `serve()` must NOT run there.
+if (import.meta.env.PROD) {
+  serve({ fetch: app.fetch, port: Number(process.env.PORT) || 3000 });
+}
+
+export default app;