Skip to content

[BUG] Not working with PayloadCMS #544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ianlibanio opened this issue Apr 7, 2025 · 0 comments
Open

[BUG] Not working with PayloadCMS #544

ianlibanio opened this issue Apr 7, 2025 · 0 comments
Labels
bug Something isn't working triage

Comments

@ianlibanio
Copy link

Describe the bug

I am trying to use PayloadCMS with opennextjs-cloudflare. While running in dev mode everything works fine, but when trying to preview or deploy, when accessing any route it gives an error (Error: The Node.js process.exit(1) API was called. Canceling the request.) and no more info is provided.

Steps to reproduce

Just create a simple payloadcms project and try to deploy it using opennextjs-cloudflare, and it won't work.

Here is an minimal reproducible example:

https://github.com/ianlibanio/test-payloadcms-cloudflare

Expected behavior

It's expected for PayloadCMS to work with opennextjs-cloudflare.

@opennextjs/cloudflare version

1.0.0-beta.1

Wrangler version

4.8.0

next info output

Using vars defined in .dev.vars
▲ [WARNING]                             You have defined bindings to the following internal Durable Objects:

                                - {"name":"NEXT_CACHE_DO_QUEUE","class_name":"DOQueueHandler"}
                                These will not work in local development, but they should work in production.
  
                                If you want to develop these locally, you can define your DO in a separate Worker, with a
  separate configuration file.
                                For detailed instructions, refer to the Durable Objects section here:
  https://developers.cloudflare.com/workers/wrangler/api#supported-bindings


workerd/server/server.c++:1942: warning: A DurableObjectNamespace in the config referenced the class "DOQueueHandler", but no such Durable Object class is exported from the worker. Please make sure the class name matches, it is exported, and the class extends 'DurableObject'. Attempts to call to this Durable Object class will fail at runtime, but historically this was not a startup-time error. Future versions of workerd may make this a startup-time error.
/bin/sh: line 1: yarn: command not found

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sat Mar 29 01:29:31 UTC 2025
  Available memory (MB): 15939
  Available CPU cores: 6
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 10.7.0
Relevant Packages:
  next: 15.2.4 // Latest available version is detected (15.2.4).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Additional context

No response

@ianlibanio ianlibanio added bug Something isn't working triage labels Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

1 participant