Issues Deploying Payload 3 (Beta) App

[atomic kettle]

Hi, guys,
Currently, I have been developing a Payload 3 application. I've been trying to deploy it, but I'm facing many problems.
If anyone knows how to deploy a Payload 3 (beta) app, any help would be appreciated. Or if someone knows whether it's not possible because it's still in beta, that information would also be helpful.

[lyric dirge]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• What is Payload? - What does "headless" mean? - Why Payload?
• Implementing Live Preview in your app - Vue
• Local API - Next.js Conflict with Local API
• Preventing Production API Abuse - Introduction - Max Depth

Community-Help:

• Best place for a studio to deploy a growing number of Payload projects?
• deploy to GCP

[placid sorrel]

It's possible, of course. 🙂 Can you give me details on what kind of errors?

[red mountain]

What beta version? Where do you deploy to? Might be connected: https://github.com/payloadcms/payload/issues/8835 Beta deployment worked on Payload Cloud without issues,

[atomic kettle]

i'm trying to deploy in vercel

This is the error

I think the scripts in package.json are not configured correctly

Esto es lo que tengo en el package.jason

  "scripts": {
    "build": "cross-env NODE_OPTIONS=--no-deprecation next build",
    "dev": "cross-env NODE_OPTIONS=--no-deprecation next dev",
    "dev:prod": "cross-env NODE_OPTIONS=--no-deprecation rm -rf .next && pnpm build && pnpm start",
    "generate:importmap": "cross-env NODE_OPTIONS=--no-deprecation payload generate:importmap",
    "generate:types": "cross-env NODE_OPTIONS=--no-deprecation payload generate:types",
    "ii": "cross-env NODE_OPTIONS=--no-deprecation pnpm --ignore-workspace install",
    "lint": "cross-env NODE_OPTIONS=--no-deprecation next lint",
    "lint:fix": "cross-env NODE_OPTIONS=--no-deprecation next lint --fix",
    "payload": "cross-env NODE_OPTIONS=--no-deprecation payload",
    "reinstall": "cross-env NODE_OPTIONS=--no-deprecation rm -rf node_modules && rm pnpm-lock.yaml && pnpm --ignore-workspace install",
    "start": "cross-env NODE_OPTIONS=--no-deprecation next start"
  },

[red mountain]

That might be it, don't know. Have you had a look in the Vercel templates, maybe they can give a hint, although they could be out of date: https://github.com/payloadcms/payload/tree/beta/templates It's beta--113, right? If you bumped Next and React according to https://github.com/payloadcms/payload/releases/tag/v3.0.0-beta.111 I'm out of ideas.

[pliant plume]

Seems like a package you're installing isn't happy with the version of React you're using.

You can force npm to ignore peer dependency conflicts if you think it's fine with npm install --legacy-peer-deps.

You'll need to update the install command in your Vercel project settings.

But obviously have to be careful doing this in production

[pliant plume]

@atomic kettle did you manage to fix this?