Vue 3.2.25 and above reintroduce a Vue 2 feature that had been
temporarily removed in Vue 3, so staying on a Vue 3 version before
3.2.25 causes unnecessary compatibility problems. (The behavior change
in question isn’t well documented – see [1] – but seems to be related to
the behavior of refs inside v-for.)
(Note that we’re still on the compatibility build, this commit isn’t
changing that yet.)
[1]: https://github.com/vuejs/v3-migration-guide/issues/10
Bug: T304717
Change-Id: I9b517b66edc6356079c49cb3ece0373c8284c2d3
* Upgrade Vue to @vue/compat version 3.2.23
* Migrate Vue.createMwApp to Vue 3 API
* Add backwards-compatible wrapper emulating Vue 2 behavior for
new Vue( { el: '#foo', ... } ) and
new Vue( ... ).$mount( '#foo' )
* Make @vue/composition-api an alias for vue, for b/c
* Convert resources/src/vue/ to ES6
* Ignore resource/src/vue/ for jsduck, since it doesn't support ES6
* VueComponentParser: Remove check for only one root node
Bug: T251974
Co-Authored-By: Lucas Werkmeister <lucas.werkmeister@wikimedia.de>
Depends-On: Ica0c0d0d6247383796d39199e50a9aff917f5b53
Change-Id: Ibd618765f962f57984994604c61b1aff9e6a778d
Debian wants us to have unminified versions of any minified code we
release. Vue doesn't publish the unminified version of this file (and
vue.common.dev.js isn't the same, because it contains additional
debugging code), so I had to build it myself.
For more info and build instructions, see resources/lib/vue/BUILD.md
Bug: T257878
Change-Id: If075d0d60848f98dc9d53e2f0a1e2d9cc4c6e510
Uses the development build of Vue in debug mode or when
$wgVueDevelopmentMode = true , and the production mode otherwise.
Change-Id: I2ab1f6364a302c0d1dbbd4c01967028c2e08082b
