vuesion VS apollo

I use them in all of my input components: https://github.com/vuesion/vuesion/tree/next/src/components/input-and-actions

I can provide you with my knowledge about Vue 2/nuxt2: https://github.com/vuesion/vuesion and Vue 3/nuxt3: https://github.com/vuesion/vuesion5

https://github.com/vuesion/vuesion or for nuxt3/vue3: https://github.com/vuesion/vuesion5

I have a repo with Vue2 (Nuxt.js 2) + composition api and storybook: https://github.com/vuesion/vuesion

https://github.com/vuesion/vuesion has GQL setup included

one exception is using plugins like i18n, they can also be used inside presentational components because they are pretty easy to integrate (no specific set of configuration per use-case) into storybook and tests. if you want to see my setup, go to https://github.com/vuesion/vuesion

I have a nuxt2 boilerplate that uses composition api already. Should hopefully be easy to migrate to nuxt3 later this year: https://github.com/vuesion/vuesion. I hope it helps you to make a decision

We maintain a (nuxt) template project that new projects are forked from. It contains all the settings and libraries that we minimally need for an app. I think it's important to have your own template project, rather than use someone else's.

Give this a shot: https://github.com/vuesion/vuesion

I maintain a reference project as boilerplate here: https://github.com/vuesion/vuesion. let me know if you have any questions.

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?