Feature Set, Vue CLI and some general question

[atomfrede]

• What features do we want to support?
• Should we build upon vue-cli and if yes which feature do we select?
• Do we want to use typescript or not?
• How to start best? Doing a sample jhipster project without client and build vue(cli) based client on that?

What do you think?

[sahbi-ktifa]

I created a sample jhipster project, redoing all components as Angular ones :

• I used Axios as recommended by Vue documentation for http request
• Vuelidate for form validation
• VueI18n for dynamic translation
• VueCookie ans VueX to maintain app state
• Webpack configurations were inherited from vue-cli but can clearly be enhanced
• Finally, I did not used TypeScript but regular JavaScript

I should add my work on a fork to let you review it (of course, it's only a draft at the moment, and should be challenged). I'll do it asap.

[atomfrede]

Sounds great. We are using a similar stack except VueX as we have quite small micro frontends so not much state management required. I would also go with plain javascript instead of typescript 👍

[gurbirdhillon]

Here are my thoughts:

• Vue-Cli is good as it can take care of lot of boiler plate setup.
• VueX is nice to have but don't really essential.
• I would also go with plain javascript instead of typescript (preferred by VueJs community)
• Axios is also my fav for http request.

I also like @sahbi-ktifa ‘s setup.

[sendilkumarn]

I like @sahbi-ktifa setup, it does cover most of our wanted features.

Vue-CLI is a good option, but based on our experiences / discussions / opinions with Angular CLI and CRA. Let us not take that.

👍 for JavaScript but Vue 3 will have a complete focus on TypeScript (so we will surely have a discussion that time whether we want to switch to that) - Just a heads up.

[deepu105]

I agree with most of it and let's start with what @sahbi-ktifa has. Let's go with what is most used in the Vue community. I think its good to start with VueX as most of the real-world use cases would end up needing some state management. If Vue CLI is useful let's use it but we also need to ensure that the Vue support closely follows Angular/React as well to avoid defragmentation.

Regarding TS vs JS, though I was not a fan of transpiling type systems, after using TS for almost a year I really like it (when used practically and not being a type nazi) its really helpful in code management/refactoring etc and I guess will help our community which is mainly back-end people. SO if possible I would like to stick to TS as we do the same for Angular and React. And as @sendilkumarn pointed out if Vue 3 is gonna focus on TS then as Hipsters we should start that already 😉
btw @sendilkumarn can you share some link on the news about TS focus on Vue?

[gurbirdhillon]

Here is quick read/benefits for using vue-cl version 3.
https://medium.com/the-vue-point/vue-cli-3-0-is-here-c42bebe28fbb

[deepu105]

In that case we could use Vue CLI with typescript

[hdurix]

I currently work on a Vue.js application integrated with JHipster as well. Here are the technologies we chose:

• Vue CLI (really useful and we didn't notice any limitation until now, webpack can still be configured for extra needs), it could be the good project to try to use a CLI and see what solution is best.
• Typescript (it does work very well with Vue, expect it sometimes needs a few tweaks, especially for unit tests) & TSLint
• Jest for unit tests (coverage is well integrated with Vue CLI, as opposed to mocha + chai solution / however some troubles with cache)
• Cypress for e2e tests (no problem using it, it works like a charm)
• Axios for HTTP requests

[atomfrede]

+1 so Vue CLI with typescript, jest and cypress and tslint it is.

[deepu105]

For e2e wouldnt it be easier to just use the protractor tests from the react client as I believe it can just work as it is without any major change

[hdurix]

I agree with @deepu105, if the couple vue+protractor is working, we should use protractor instead of cypress.

[atomfrede]

Let's see how it works. I would suggest lets start and maybe give cypress a try as it is the preferred solution in the vue community, so if it works we don't need to maintain special configuration for protractor (writing tests is imho easiert) and we can rely on the power of the vue community and it might attract more vue developers to contribute (maybe).

[deepu105]

@atomfrede I was thinking of a quick win so that we can reuse the same templates from React instead of maintaining another set of templates. I was even thinking of moving all the e2e tests out and reusing the same for Angular and React since they are pretty much similar

[atomfrede]

@deepu105 Yes makes totally sense. Maybe just let's get started and not too much thinking about what we use for e2e testing now and decide when we need to. There is much work we need to do before.