feat(devtools): add KV, Blob, Cache management UI

[onmax]

Summary

Switch NuxtHub DevTools KV/Blob/Cache tabs to a hosted UI loaded via iframe (no separate UI bundle shipped from @nuxthub/core). Functionality stays the same; only the UI delivery changes.

How It Works

• DevTools tabs iframe the hosted pages on hub.nuxt.com.
• We pass ?url=<localOrigin> so the hosted UI can call back into your local app.
• Local origin detection is robust (uses Nuxt devServer URL/port + CLI argv fallbacks) and supports an escape hatch: hub.devtools.appOrigin.
• Adds /api/_hub/* compatibility endpoints + CORS so the hosted UI can call http://localhost:<port>/api/_hub/....

Limitations

• Requires internet to load the hosted UI.
• Safari currently blocks https://... iframes calling http://localhost... (mixed content). See nuxt-hub/core#34 (comment).

Closes #774

TODO (Before Merge)

• Update the deployment on hub.nuxt.com (hosted DevTools embed) and test it
• Take screenshots and update the docs

[vercel]

@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxthub/core@776

commit: 74e490c

[RihanArfan]

Looks good! My feedback after seeing the video:

• We could style Nuxt UI colours to match the Nuxt DevTools. Nuxt UI is nice and has additional components that the Nuxt DevTools UI Kit doesn't include https://github.com/nuxt/devtools/tree/main/packages/devtools-ui-kit/src/components
• Destructive actions like mass deleting files should have a confirmation

[onmax]

@RihanArfan added your feedback :)

[RihanArfan]

Hey, was facing some issues running it due to missing imports for useRouter, useFetch and navigateTo from #app in the Vue pages.

Besides that, functionality seems all good

[onmax]

@RihanArfan fixed the missing #app imports (useFetch/useRouter/navigateTo) in the devtools client pages. The runtime error you hit should be resolved now. Thanks for the catch!

[onmax]

@atinux

Switched the NuxtHub DevTools storage tabs (KV/Blob/Cache) to use the hosted UI embedded as an iframe from hub.nuxt.com/devtools/. The hosted UI calls back into the local app via ?url=<localOrigin>.

• No more separate DevTools UI bundle shipped from @nuxthub/core (only server endpoints + tab registration)
• localOrigin now prefers nuxt.options.devServer.url (actual listening port) and supports hub.devtools.appOrigin override
• Added /api/_hub/* compatibility endpoints + CORS for https://hub.nuxt.com -> localhost
• Safari limitation still applies (mixed content): nuxt-hub/core#34 (comment)

[onmax]

I merged the latest main into this branch locally.

At the moment, the hosted DevTools pages on hub.nuxt.com still unavailable, so I couldn’t verify the iframe flow end-to-end.

Is there anything else you would like me to check to help move this PR forward? Also, I'd appreciate guidance on the preferred direction here:

1. should we keep the current hosted-iframe implementation,
2. or would you prefer a dual approach with a local Nuxt UI in development and the hosted UI only where it makes sense?

Thank you!