-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flow support #1810
Comments
Not a bad idea... |
Maybe in the next version, let's release 3.0.0 first! 😸 |
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. |
And I don't think it's a valid use case, as few "less advanced developers" would choose flow for their Vue projects... |
We will not do this in core. Our typing focus will be on TS. |
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).
The text was updated successfully, but these errors were encountered: