-
Notifications
You must be signed in to change notification settings - Fork 57
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
Cloudflare Browser Rendering worker not showing up #381
Comments
This is the code in my API route, for reference:
And here is my
|
How did you deploy your project, using the NuxtHub or the NuxtHub admin? |
I configured everything through the admin initially. Let me try running through |
I ran I'll continue to debug this and report back what I find. Just wanted to make sure there wasn't anything obvious I was missing. |
Keep me updated, this is quite annoying :( |
Will do, appreciate the quick reply |
I figured out the issue, it was complete user error on my part. My API route that was using hubBrowser() was returning a response before the browser could initiate. It worked locally because it was running in the background after returning a response. After fixing that, everything worked without a hitch. Sorry for the false alarm! |
Describe the bug
I configured browser rendering using the hub config and
hubBrowser()
. It's working locally but when deploying, the browser rendering page in Cloudflare is empty and my API endpoint is not executing the functionality usinghubBrowser()
. I looked in the docs and searched the issues here, but sorry if I missed something.Is there anything else I need to do to get browser rendering set up besides setting
browser: true
in the hub config?Steps to reproduce
Steps to reproduce the behavior:
browser: true
tohub
innuxt.config.ts
. In my API route, usehubBrowser()
When I test on prod, the function silently does not handle anything after initiating
hubBrowser()
. I have a few console statements printing just to help debug, and only see the one that prints beforehubBrowser()
is initiated.The text was updated successfully, but these errors were encountered: