What problem does this feature solve?
Adding flow, for less advanced developers, might be tricky. There are several things to do: install npm dependencies, configure babel, configure ESlint (optional).
What does the proposed API look like?
Flow should be available on the features selection step. It should be available only when TypeScript is disabled (and the opposite: TypeScript should be disabled when Flow is enabled).
wujekbogdan
All 5 comments
Not a bad idea...
andreydos
on 11 Jul 2018
Maybe in the next version, let's release 3.0.0 first! 馃樃
Akryum
on 11 Jul 2018
I'm no sure if we should even maintain both type systems in cli core.
While we actually use flow in the vue core and router repositories at the moment, we are in the process of switching over to typescript more and more (Vue 3 will be rewritten in TS, amongst other things), and I think our team's kowledge of typescript is much deeper that for flow with people such as @ktsn on board.
So I would even be inclined to say this should be provided by the community, and we focus on the type system that we "build" on in the future.
LinusBorg
on 13 Jul 2018
And I don't think it's a valid use case, as few "less advanced developers" would choose flow for their Vue projects...
sodatea
on 13 Jul 2018
We will not do this in core. Our typing focus will be on TS.
yyx990803
on 13 Jul 2018
Related issues
williamstar
路
79Comments
ghenry
路
40Comments
dimavolo
路
75Comments
yyx990803
路
80Comments
wuyuweixin
路
35Comments
Most helpful comment
I'm no sure if we should even maintain both type systems in cli core.
While we actually use flow in the vue core and router repositories at the moment, we are in the process of switching over to typescript more and more (Vue 3 will be rewritten in TS, amongst other things), and I think our team's kowledge of typescript is much deeper that for flow with people such as @ktsn on board.
So I would even be inclined to say this should be provided by the community, and we focus on the type system that we "build" on in the future.