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
Currently this project is only Nuxt2, and I think Diizzayy's is Nuxt3 only. We have been working on Nuxt 3/4 version as we speak actually.
But I'm actually seriously considering dropping WP-GraphQL integration... It's just been terrible for performance (so expensive to host at scale) and stability problems have been huge for us. The Gutenberg blocks are very brittle, a small change in the data structure by WordPress and everything breaks... Really looking hard at just going back to vanilla WP-JSON API and a OpenAPI 3.x doc generator plugin. Curious what you think about that?
As for Dizzayy's client, I really like Diizzayy, he's actually helping us with our Nuxt3 migration work. But I like the raw nature of Gomah's plugin, it's very easy to tell what is going on. Diizzayy's GqlFunctions are a bit too magic for me, kind of requires you know whats going on to understand where all those functions are coming from... But Nuxt 3 has a lot of these magic imported functions so maybe I just have to get used to them...
I use WP-GraphQL for WooCommerce, and as you mentioned, I have never used other APIs before. I am asking you this because I am working on a dynamic e-commerce project called nuxtcommerce.netlify.app, and I can't decide whether to use Diizzayy's or Gomah's.
Yes, as you said, a cheap hosting provider greatly affects performance on a large scale.
Diizzayy keeps his module constantly updated. I was using his other module, nuxt/apollo, but the new update caused different problems and it no longer works on it. On the other hand, it's uncertain whether Gomah will update his module or if it will stay as it is.
Hi @drewbaker,
Wouldn't it be better to use Diizzayy/nuxt-graphql-client instead of gomah/nuxt-graphql-request in this project?
Best regards,
The text was updated successfully, but these errors were encountered: