How to deploy on vercel?

[digoburigo]

When trying to deploy to Vercel it's building normally

But getting this type error after build

Tried a lot of different ways but nothing works.

References
honojs/hono#1256
vercel/examples#1213

[nktnet1]

hmm - the demo site (https://rtstack.nktnet.uk) only deploy the Web Frontend to vercel.

The backend server uses Docker deployment instead of serverless.

---

Regardless, I can reproduce this locally using vercel build:

It appears that vercel build runs into a lot of type errors - potentially due to not using @types/node definition of Request and Response (and thus request.headers or response.body breaks).

To hackily patch the type errors with as any, you can make the following changes:

click to view

diff --git a/apps/server/src/index.ts b/apps/server/src/index.ts
index 725fd4c..afd9d37 100644
--- a/apps/server/src/index.ts
+++ b/apps/server/src/index.ts
@@ -74,7 +74,7 @@ app.use(
   async (c, next) => {
     const { matched, response } = await api.handler(c.req.raw);
     if (matched) {
-      return c.newResponse(response.body, response);
+      return c.newResponse((response as any).body, response);
     }
 
     await next();
diff --git a/packages/api/src/server/index.ts b/packages/api/src/server/index.ts
index 51c42b7..c65bf3d 100644
--- a/packages/api/src/server/index.ts
+++ b/packages/api/src/server/index.ts
@@ -68,7 +68,7 @@ export const createApi = ({
         context: await createORPCContext({
           db,
           auth,
-          headers: request.headers,
+          headers: (request as any).headers,
         }),
       });
     },
diff --git a/packages/db/src/schemas/posts.ts b/packages/db/src/schemas/posts.ts
index 139baa6..cb9e3f4 100644
--- a/packages/db/src/schemas/posts.ts
+++ b/packages/db/src/schemas/posts.ts
@@ -5,8 +5,8 @@ import { user } from './auth';
 
 export const post = pgTable('post', (t) => ({
   id: t.uuid().primaryKey().defaultRandom(),
-  title: t.varchar({ length: 256 }).notNull(),
-  content: t.text().notNull(),
+  title: t.varchar({ length: 256 }).notNull() as any,
+  content: t.text().notNull() as any,
   createdAt: t
     .timestamp({ mode: 'string', withTimezone: true })
     .notNull()
@@ -22,5 +22,5 @@ export const CreatePostSchema = v.omit(
     title: v.pipe(v.string(), v.minLength(3), v.maxLength(256)),
     content: v.pipe(v.string(), v.minLength(5), v.maxLength(512)),
   }),
-  ['id', 'createdAt', 'createdBy'],
+  ['id', 'createdAt', 'createdBy'] as any,
 );

This will allow vercel build to succeed.

Naturally, you will get many runtime errors when deploying and running in production, but hopefully that helps with further investigation into the issue.

---

As I don't typically deploy backends to Vercel, I suggest chasing this issue with vercel (or potentially hono/oRPC) to see if they have a resolution.