Real advantages of `@nuxthub/core` compared to separate implementations

[oritwoen]

I started wondering what the significant differences are between using @nuxthub/core and native functions from unjs/nitro and packages from the unjs ecosystem and from pi0.

I recently looked at the documentation https://nitro.unjs.io/ and https://github.com/pi0/nitro-cloudflare-dev and it seems that it is possible to handle almost everything without nuxthub easily (at least for me).

At this point I started to see @nuxthub/core as a wrapper that connects everything and has convenient composables.

Of course, there is also admin.hub.nuxt.com which cannot be handled in any other way and requires a hub. Apart from that I don't see any significant differences. At the moment, I don't really see a need to use it and the idea of sharing customer data with an external platform doesn't appeal to me.

I have used @nuxthub a bit and it is great, but I am currently testing implementations with just nitro without using a hub and experimenting to see if working without proxies and wrappers and an individual approach to each composable will be better for me when implementing my systems.

I will be grateful @Atinux for even a loose comparison of the capabilities of the hub and nitro/unjs itself and referring to what I wrote.

[atinux]

Hey @oritwoen and thank you for your feedback.

At the current stage, you can do the same as what @nuxthub/core offers using nitro-cloudflare-dev (we use it under the hood) and use the bindings, what you will miss are:

• The remote storage to connect to you production / staging data in development
• The admin UI
• More complex composable that we are working on (see #71 and #99)
• The automatic creation & configuration of your bindings when deploying your project

Of course, we do plan to add business features on top of this foundation such as authenticaiton, emails, etc.

At the moment, I don't really see a need to use it and the idea of sharing customer data with an external platform doesn't appeal to me.

I am not sure to understand, with the Admin, you deploy your projects on your Cloudflare account, so we don't have access to your customer data. The project, d1, r2 and kv are on your CF account.

You don't need to use NuxtHub if you don't want to, this is an extension of Nuxt to help you ship fullstack application at a fast pace and with confidence.

Before working on NuxtHub, I was actually doing everything myself (see https://github.com/Atinux/nuxt-todos-edge/tree/1459725545b239fb27827d8e1a2571c2de3f5b4d)

[oritwoen]

Thanks for the answers @Atinux. Now everything is a bit simpler and more understandable for me.

To avoid being a masochist, after experiments and tests with nitro, I will definitely return to @nuxt-hub because it will simply be the most convenient.

As for the admin panel itself, it would be great if it became open source in the future. I could make it self-hosted, for example, in my infrastructure or refine it to suit my own needs.

At the moment, I don't really see a need to use it and the idea of sharing customer data with an external platform doesn't appeal to me.

Regarding this, however. I assumed so (possibly incorrectly) because when I opened nuxt's devtools and checked the source of the page, I noticed that, for example, displaying the database takes place by displaying an iframe from the following URL:

https://admin.hub.nuxt.com/embed/database?url=

And I thought that this data must be shared with a third party to be displayed since it's an iframe.

[atinux]

Actually https://admin.hub.nuxt.com/embed/database?url= simply call your localhost.

I use it directly because all the UI components for the admin are there 😊

The admin might be open source one day, but it's still too early to decide IMO