Add Vercel deployment guide for MSW and Server modes by Copilot · Pull Request #658 · objectstack-ai/framework

Copilot · 2026-02-13T05:04:10Z

Documents how to deploy ObjectStack applications to Vercel in two modes: MSW (static SPA with in-browser kernel) and Server (Serverless Functions with real database).

Changes

content/docs/guides/deployment-vercel.mdx — New guide covering:
- MSW mode: Vite SPA deployment — kernel bootstrap in browser, MSW Service Worker setup, vercel.json with SPA rewrites, monorepo config
- Server mode (Next.js): @objectstack/nextjs catch-all route handler with kernel singleton pattern
- Server mode (Hono Edge): HttpDispatcher-based routing on Vercel Edge Functions
- Environment variables, runtime mode switching (?mode=msw|server), deployment checklists, feature comparison table
content/docs/guides/meta.json — Added deployment-vercel to Operations section
content/docs/guides/index.mdx — Added guide to Operations table

Key patterns documented

MSW mode (vercel.json):

{
  "framework": "vite",
  "build": { "env": { "VITE_RUNTIME_MODE": "msw" } },
  "rewrites": [{ "source": "/(.*)", "destination": "/index.html" }]
}

Server mode (Next.js catch-all):

// app/api/[...objectstack]/route.ts
import { createRouteHandler } from '@objectstack/nextjs';
const handler = async (...args) => {
  const kernel = await getKernel();
  return createRouteHandler({ kernel, prefix: '/api' })(...args);
};
export { handler as GET, handler as POST, handler as PATCH, handler as DELETE };

Original prompt

objectstack应用如何以最佳的方式部署的vercel，包括msw模式和server模式。

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

vercel · 2026-02-13T05:04:15Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectstack-play	Canceled		Feb 13, 2026 9:13am
spec	Canceled		Feb 13, 2026 9:13am

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Copilot

Pull request overview

Adds a new deployment guide describing how to deploy ObjectStack apps to Vercel in two modes—MSW (static SPA) and Server (serverless/edge)—and wires it into the Guides navigation.

Changes:

Added a new “Deploy to Vercel” guide covering MSW mode and server-mode options (Next.js + Edge/Hono).
Registered the new guide in the Guides sidebar metadata (Operations section).
Linked the guide from the Guides index Operations table.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
`content/docs/guides/deployment-vercel.mdx`	New Vercel deployment guide with MSW + server/edge patterns, env vars, and checklists
`content/docs/guides/meta.json`	Adds `deployment-vercel` under the Operations section
`content/docs/guides/index.mdx`	Adds “Deploy to Vercel” link to the Operations table

Copilot · 2026-02-13T05:19:37Z

+      result = await dispatcher.handleData(subPath, method, body, queryParams, {});
+      break;
+    case 'meta':
+      result = await dispatcher.handleMetadata(subPath, {}, method, body);


HttpDispatcher.handleData/handleMetadata expect a context with at least { request: ... } (used for broker call options, auth, etc.), but this example passes {}. That can break features that rely on request context (sessions, headers, IP, tracing). Pass the underlying request (or a minimal context object) through to the dispatcher methods.

Suggested change

result = await dispatcher.handleData(subPath, method, body, queryParams, {});

break;

case 'meta':

result = await dispatcher.handleMetadata(subPath, {}, method, body);

result = await dispatcher.handleData(subPath, method, body, queryParams, { request: c.req });

break;

case 'meta':

result = await dispatcher.handleMetadata(subPath, { request: c.req }, method, body);

Copilot · 2026-02-13T05:19:38Z

+  // Dispatch based on first segment (data, meta, auth, etc.)
+  const body = ['POST', 'PATCH', 'PUT'].includes(method)
+    ? await c.req.json().catch(() => ({}))
+    : {};
+
+  const subPath = segments.slice(1).join('/');
+  let result;
+
+  switch (segments[0]) {
+    case 'data':
+      const queryParams: Record<string, any> = {};
+      url.searchParams.forEach((v, k) => (queryParams[k] = v));
+      result = await dispatcher.handleData(subPath, method, body, queryParams, {});
+      break;
+    case 'meta':
+      result = await dispatcher.handleMetadata(subPath, {}, method, body);
+      break;
+    default:
+      return c.json({ error: 'Not Found' }, 404);
+  }


The comment says the catch-all dispatches based on the first segment “(data, meta, auth, etc.)”, but the switch only implements data and meta. Either expand the example to handle the other protocol segments (auth/graphql/storage/...) or adjust the wording so it matches what the code actually does.

Copilot · 2026-02-13T05:19:38Z

+
+export const GET = handle(app);
+export const POST = handle(app);
+export const PATCH = handle(app);


This Edge Function example prepares to accept PUT requests (it parses JSON for PUT), but the exported handlers omit PUT, so Vercel will not route PUT requests to the app. Export PUT (and any other required methods) alongside GET/POST/PATCH/DELETE.

Suggested change

export const PATCH = handle(app);

export const PATCH = handle(app);

export const PUT = handle(app);

Copilot · 2026-02-13T05:19:38Z

+  return routeHandler(...args);
+}
+
+export { handler as GET, handler as POST, handler as PATCH, handler as DELETE };


Next.js App Router needs explicit exports for each HTTP method. createRouteHandler supports PUT (used for metadata writes), but this example only exports GET/POST/PATCH/DELETE, so PUT requests will return 405. Export PUT as well (and any other methods you intend to support).

Suggested change

export { handler as GET, handler as POST, handler as PATCH, handler as DELETE };

export { handler as GET, handler as POST, handler as PUT, handler as PATCH, handler as DELETE };

Copilot · 2026-02-13T05:19:39Z

+### Option B: Hono on Vercel Edge
+
+Use the `@objectstack/hono` adapter for lightweight Edge Function deployments:
+
+```typescript
+// api/[...route].ts  (Vercel Edge Function)
+import { Hono } from 'hono';
+import { handle } from 'hono/vercel';
+import { ObjectKernel, DriverPlugin, AppPlugin, HttpDispatcher } from '@objectstack/runtime';


This section says to use the @objectstack/hono adapter, but the package currently only exposes objectStackMiddleware() and does not provide a route handler/dispatcher integration. The example also doesn’t import anything from @objectstack/hono, so readers can’t actually follow the instruction as written. Either update the text to describe the manual HttpDispatcher approach, or update the example to use the adapter API (once it exists).

Copilot · 2026-02-13T05:19:39Z

+// Catch-all route — delegates to HttpDispatcher
+app.all('/*', async (c) => {
+  const k = await getKernel();
+  const dispatcher = new HttpDispatcher(k);
+  const method = c.req.method;


The Hono Edge example instantiates HttpDispatcher, but HttpDispatcher is marked @deprecated in @objectstack/runtime with guidance to use createDispatcherPlugin() instead and a note that it will be removed in v2. Publishing a deployment guide that depends on a deprecated API is likely to age poorly; consider switching the guide to the recommended non-deprecated approach, or explicitly label this option as legacy/temporary with a migration note.

Initial plan

b3b1886

Copilot AI assigned Copilot and hotlong Feb 13, 2026

Copilot started work on behalf of hotlong February 13, 2026 05:04 View session

Copilot AI and others added 2 commits February 13, 2026 05:08

Add Vercel deployment guide covering MSW and Server modes

1e1cabf

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Address code review: add AppPlugin, fix Hono Edge example

b531984

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add deployment instructions for Objectstack on Vercel~~ Add Vercel deployment guide for MSW and Server modes Feb 13, 2026

Copilot AI requested a review from hotlong February 13, 2026 05:10

Copilot finished work on behalf of hotlong February 13, 2026 05:10

hotlong marked this pull request as ready for review February 13, 2026 05:13

Copilot AI review requested due to automatic review settings February 13, 2026 05:13

Copilot started reviewing on behalf of hotlong February 13, 2026 05:13 View session

hotlong merged commit 9237500 into main Feb 13, 2026
5 of 7 checks passed

Copilot AI reviewed Feb 13, 2026

View reviewed changes

vercel bot deployed to Preview – objectstack-play February 13, 2026 09:10 View deployment

vercel bot deployed to Preview – spec February 13, 2026 09:13 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Vercel deployment guide for MSW and Server modes#658

Add Vercel deployment guide for MSW and Server modes#658
hotlong merged 3 commits intomainfrom
copilot/optimize-vercel-deployment

Copilot AI commented Feb 13, 2026 •

edited

Loading

Uh oh!

vercel bot commented Feb 13, 2026 •

edited

Loading

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	export const PATCH = handle(app);
	export const PATCH = handle(app);
	export const PUT = handle(app);

	export { handler as GET, handler as POST, handler as PATCH, handler as DELETE };
	export { handler as GET, handler as POST, handler as PUT, handler as PATCH, handler as DELETE };

Conversation

Copilot AI commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Key patterns documented

Uh oh!

vercel bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Feb 13, 2026 •

edited

Loading

vercel bot commented Feb 13, 2026 •

edited

Loading