- ESLint has released v6, should upgrade, contribution welcome
vue upgrade
, almost done, needs tests, assigned to myself, expected to get it done before Thursday. After that we should start writing migration documentation.- Make vuex & vue-router standalone plugins vuejs/vue-cli#4196
- PWA plugin UI (follow up of vuejs/vue-cli#2981)
- Possible Jest regression vuejs/vue-cli#4051 (comment)
-
Plugin Ordering
After thinking about this, I realized it's not that urgent than I previously thought. There're all kinds of workarounds for the use cases (either by hacking the API or by changing the plugin UX flow). I prefer not to touch the code base at the moment in favor of stability. We don't have that much time and energy to fix all the possible bugs coming with this big feature.
We can add this later in a feature release if we come to a consensus on the design and implementation.
-
Warn before Generator is invoked and might override uncommited changes This is needed for
vue upgrade
as we'll try to automatically migrate users' code
See:
Some issues have the "good first issue" label added but I didn't check them all so maybe there are more easy ones. There're also other "nice to have" features with the "enhancement" label, I haven't looked into them thoroughly so if you are willing to pick one up, please comment at it first.
What about extending the
hasPlugin
helper to take a second argument that accepts a version range?Seems users want the other way around. vuejs/vue-cli#2676
If the plugin didn't implement typescript generation, we should ignore it.
We can use git commit hooks instead.
I think this can be better done with helper functions like
transformScript
.