Vercel deployment failes because of import in middleware.js

[aservment]

Hi together,

I am trying to deploy the latest version of Cal.com to Vercel and unfortunately it fails with the following error message. (Node 16.x)

`
...
Done in 68.15s.

01:48:15.130 | Using TypeScript 4.6.4 (local user-provided)
01:48:51.179 | Build failed with 2 errors:
01:48:51.179 | vc-file-system:apps/web/middleware.js:3:25: error: Could not resolve "next-collect/server" (mark it as external to exclude it from the bundle, or surround it with try/catch to handle the failure at run-time)
01:48:51.180 | vc-file-system:apps/web/middleware.js:4:28: error: Could not resolve "@lib/telemetry" (mark it as external to exclude it from the bundle, or surround it with try/catch to handle the failure at run-time)
01:48:56.247 | @calcom/web:build:
01:48:56.248 | @calcom/web:build: ./pages/api/auth/saml/token.ts
01:48:56.248 | @calcom/web:build: 15:17 Warning: Unexpected any. Specify a different type. @typescript-eslint/no-explicit-any
01:48:56.248 | @calcom/web:build:
...
`

I have set the following environment variables:

CALENDSO_ENCRYPTION_KEY
NEXTAUTH_SECRET
DATABASE_URL

The Build & Development Settings in Vercel I have configured like in this image:

Does anyone have any idea why the build process is not working?

Best Regards
Thomas

[lienista]

Mine was able to build with the following env vars. One important thing to note is that the GOOGLE_API_CREDENTIALS is a json, not a string. (However, if you deployed this in Railway, GOOGLE_API_CREDENTIALS is a string)This is a very small but yet significant detail. It required me to read through the build errors to discover this. It's not documented anywhere in Vercel.

[dosubot[bot]]

Hello @aservment! I'm here to help you with your deployment issue. I can assist you with bug fixes, answer your questions, and guide you on becoming a contributor.

The Vercel deployment of Cal.com is failing due to unresolved imports in middleware.js for "next-collect/server" and "@lib/telemetry". Here are the steps to resolve these issues:

1. Unresolved Import for next-collect/server: Ensure that the next-collect package is correctly installed in your project. You can do this by checking your package.json to see if next-collect is listed as a dependency and running npm install or yarn install to make sure all dependencies are installed.

2. Incorrect Import for @lib/telemetry: The import path for telemetry functions should be updated to the correct path. Change the import statement in middleware.js to:

   import { extendEventData, nextCollectBasicSettings } from "@calcom/lib/telemetry";

   This should resolve the import error for "@lib/telemetry" ^[1][2].

By addressing these import issues, your deployment should proceed without these specific errors.

To continue talking to Dosu, mention @dosu.

Written by @dosu, approved by dosu-customer-success