You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I see the message "@nuxthub/core not detected." in the bottom left corner of the NuxtHub Dashboard. This happens if the Project type is "Cloudflare Workers (new)" and when disabling the project.user.workers.dev. domain. (e.g. through the dashboard or a wrangler.jsonc/toml file).
Steps to reproduce
Steps to reproduce the behavior:
Add a custom domain to the worker, e.g by adding the following to your wrangler config file:
Expected behavior
I expected the Dashboard to show the correct status even when having the workers.dev domain disabled.
I'm assuming the dashboard is trying to access /api/_hub/manifest on the workers.dev domain, which then fails. (Cloudflare responds with Status code 522 when the workers.dev domain is disabled).
This only happens with Workers, but not with Cloudflare Pages since the pages.dev subdomain cannot be disabled there.
The text was updated successfully, but these errors were encountered:
Describe the bug
I see the message "@nuxthub/core not detected." in the bottom left corner of the NuxtHub Dashboard. This happens if the Project type is "Cloudflare Workers (new)" and when disabling the project.user.workers.dev. domain. (e.g. through the dashboard or a wrangler.jsonc/toml file).
Steps to reproduce
Steps to reproduce the behavior:
"workers_dev": false,
to your wrangler config fileExpected behavior
I expected the Dashboard to show the correct status even when having the workers.dev domain disabled.
I'm assuming the dashboard is trying to access /api/_hub/manifest on the workers.dev domain, which then fails. (Cloudflare responds with Status code 522 when the workers.dev domain is disabled).
This only happens with Workers, but not with Cloudflare Pages since the pages.dev subdomain cannot be disabled there.
The text was updated successfully, but these errors were encountered: