Next.js + PayloadCMS deployment issue: `.next` build from CI fails with dynamic dependencies

[ruby nymph]

Next.js + PayloadCMS deployment issue: .next build from CI fails with dynamic dependencies (@xenova/transformers, onnxruntime, @huggingface/jinja) but manual build on server works

What We Are Trying To Achieve

• Avoid running next build on EC2
• Keep server cost low (t3a.micro)
• Build in CI
• Deploy build artifact
• Ensure dynamic ML dependencies load correctly

[vocal heath]

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:

• Swap in your own React components - Performance - Imports best practices
• Production Deployment
• Production Deployment - Basics

Community-Help:

• Deploying payload 3.0 with docker to Coolify
• Best place for a studio to deploy a growing number of Payload projects?
• Postgres causing problem on cloudflare workers for deployment
• deploy to GCP

[radiant fossil]

try with "npm" @ruby nymph

[ruby nymph]

It's not working with npm as well @radiant fossil

[wintry mantle]

Don't think this is a payload issue.