fix(deploy): install @remotion/lambda so the Vercel build resolves the cloud-render routes

The /api/render/lambda routes import `@remotion/lambda/client`, but the
package was never added to apps/web — Turbopack failed with "Module not
found: @remotion/lambda/client", which is a hard build error that blocked
the Vercel deploy before any runtime env var is read.

- Add @remotion/lambda@4.0.459 (pinned to match the other @Remotion deps)
- Externalize it in next.config so Turbopack doesn't bundle its native side

Verified `next build` succeeds. Note: the Lambda RENDER additionally needs
AWS env vars set in the Vercel dashboard (REMOTION_AWS_REGION,
REMOTION_LAMBDA_SERVE_URL, REMOTION_LAMBDA_FUNCTION_NAME, AWS creds) — those
are a runtime concern, not a build/deploy blocker.

Author: sankalpaacharya

apps/web/next-env.d.ts

@@ -1,6 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/dev/types/routes.d.ts";
+import "./.next/types/routes.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

apps/web/next.config.mjs

@@ -11,6 +11,10 @@ const nextConfig = {
     // Turbopack try (and fail) to resolve every platform's binary statically,
     // so it must be externalized and loaded from node_modules at runtime.
     "@remotion/renderer",
+    // @remotion/lambda ships native/AWS deps; the /api/render/lambda routes
+    // only use the lightweight `@remotion/lambda/client` entry, but externalize
+    // the package so Turbopack doesn't try to bundle its native side.
+    "@remotion/lambda",
     "@remotion/tailwind-v4",
     "@tailwindcss/webpack",
     "@tailwindcss/node",

apps/web/package.json

@@ -29,6 +29,7 @@
     "@mdx-js/react": "^3.1.1",
     "@next/mdx": "^16.2.5",
     "@remotion/bundler": "4.0.459",
+    "@remotion/lambda": "4.0.459",
     "@remotion/player": "4.0.459",
     "@remotion/renderer": "4.0.459",
     "@remotion/tailwind-v4": "4.0.459",