apollo VS buefy

Is this what apollo-components is all about? https://github.com/vuejs/apollo Bulletproof is based on a REST API, so if GraphQL is the backend, this would be a great choice!

If you're set on using both Nuxt 3 and Vue Apollo, I'd recommend not using the Nuxt Apollo module, and instead integrating Vue Apollo directly: https://github.com/vuejs/vue-apollo

Cool, if you do go with graphql, I'd recommend vue-apollo on the client end. Combine with @vue/apollo-composable and graphql-codegen and it feels like sorcery.

Frontend is vuejs 2 that was scaffolded with vue-clu and is a CRUD site for the backend. I planned on using vue-apollo for the frontend to easily connect to graphql backend, I was especially excited to learn that vue-apollo handles most of the state and caching and decided to try it instead of vuex for state. I've hit a couple snags though and am beginning to think that vue-apollo isn't the right way to approach this (plus their documentation leaves much to be desired). Here's where I'm at:

You might have heard lots of buzz around GraphQL, and if you are interested in integrating it with Vue.js, then I would like to suggest you try Vue Apollo. The library makes use of Vue in the combination of GraphQL/Apollo for a smooth as well as a pleasant experience. To get startedClick here

I'm learning GraphQL and every tutorial/vid I look at in relation to using Apollo with Vue seems to involve this other package, graphql-tag. But no one ever seems to explain why it's needed, and it's not listed as a dependency of Vue Apollo. So can anyone tell me precisely why graphql-tag is needed, and whether Apollo can work with Vue without it? Essentially, is it required (and if so why isn't it listed as an Apollo dependency?) or optional?

I looked into Buefy, which has great and accessible source code btw, and my hunch was correct. See line 184 at this link: https://github.com/buefy/buefy/blob/dev/src/components/carousel/CarouselList.vue

Buefy: A lightweight UI library that provides a range of customizable UI components, including forms, buttons, and navbars.

Back in the day I used Buefy https://buefy.org/ which is a Vue version of Bulma. I like it, I'd say it was easy to implement and I could change the style a bit without too many lines of code.

I'm learning Vue and today noticed something I hadn't seen before, by Buefy component templates, namely hash-prefixed attributes on template tags e.g.

Encountered this issue as we're looking into solutions for migrating a Vue 2 + Buefy codebase over to Vue 3. The maintainer is actively working on Oruga, which for the most part, has a very similar api to Buefy components and is pretty close in terms of component parity. I only found out about Oruga through this pinned issue in the Buefy repo.

That will render any Vue components referenced within the content returned from the API. In my case, it contained Buefy component references e.g.:

I like Bulma and I've used it on most recent projects. It feels lighter and easier to customize than Bootstrap. Buefy is vue components based on Bulma. It's pretty good, but lately I've been using Livewire.

Personally I don't like either. Bootstrap seems too bloated and cookie-cutter, and Tailwind is inline styles and clutter. Lately I've used Bulma (CSS framework) and Buefy (Bulma + Vue) on a couple of projects. I also like the look of Pure CSS, but I haven't used it.

It seems that the good UI frameworks are only available for Vue 2 at present. Bootstrap (Bootstrap-vue), Semantic UI (Semantic UI Vue), Bulma (Buefy), Material (Vuetify) all only support Vue 2.

7 - Buefy