vue-enterprise-boilerplate VS vuesion

Clones, Boilerplates - Datlyfe/jira_clone - From Ben Hong and Chris Fritz - bencodezen/vue-enterprise-boilerplate

Vue enterprise boilerplate

The next step is to create a BaseModal component. You can name it whatever you like. I like to build my apps based on the Vue Enterprise Boilerplate- which is where the name BaseModal comes in.

Also have a look at this template maybe, much to learn from it: https://github.com/bencodezen/vue-enterprise-boilerplate

In this category is https://github.com/chrisvfritz/vue-enterprise-boilerplate

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.