fix: handle nitro-cloudflare-dev Promise bindings#742
Conversation
|
@onmax is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
4d07903 to
757e725
Compare
|
Thanks for the help on this @onmax Did you see that with latest Nitro compat, we don't need to install |
|
I will be offline for the next week. Please feel free to iterate or close this PR if a better solution emerges. Merry Christmas to the whole team! And well done on this new NuxtHub; I'm really excited about everything that's happening in the Nuxt ecosystem! 2026 will be 🔥 |
|
I will let @RihanArfan have a deep review at it once he's back from holidays :) |
07128ba to
5617264
Compare
|
I think release 0.10 without this PR is beta, because many feature still not migrated without this PR |
- Add `hub.remote` option to use production Cloudflare bindings during dev - Fix Promise bindings from nitro-cloudflare-dev via getPlatformProxy - Change db import to dynamic to handle async bindings - Add isRemoteDev helper to reduce duplication - Fail loudly when remote bindings fail (no silent stub fallback) - Fix proxy.dispose() to actually call the function Fixes nuxt-hub#741 Fixes nuxt-hub#743
5617264 to
657c0f4
Compare
3 participants
Superseded
This PR has been superseded by: