Change Details

=== Background **[[https://pinia.vuejs.org/|Pinia]] is the successor to Vuex**. It promises to be lighter weight than Vuex (6KB for Pinia 2.0.13, 15KB for Vuex 4.0.2) and to support TypeScript better. The main challenge we'd have to address in order to use Pinia is that Pinia is mostly compatible with Vuex 4, but not entirely. The API for creating a store is different (we could probably add a compatibility wrapper for this), and mutations don't exist in Pinia. Modifying code written for Vuex 4 such that it would work with both Vuex 4 and Pinia, or adding compatibility wrappers so that Vuex 4 code works with Pinia (which would be required for a smooth migration from Vuex to Pinia) may or may not be easy. To install Pinia in MediaWiki, we would probably want to use `pinia.iife.prod.js` / `pinia.iife.js` and wrap them so that `VueDemi` is aliased to `require( 'vue' )`. Alternatively, we could use `pinia.prod.cjs`, but then we would have to set up a module alias for `vue-demi` to redirect to `vue`, and we would have to make `@vue/devtools-api` available (in the iife versions, that package is inlined). ==== Pending security review {T308495}

=== Background **[[https://pinia.vuejs.org/|Pinia]] is the successor to Vuex**. It promises to be lighter weight than Vuex (6KB for Pinia 2.0.13, 15KB for Vuex 4.0.2) and to support TypeScript better. We could not immediately replace Vuex 4 with Pinia, because Pinia isn't fully backwards compatible with Vuex 4. The APIs are reasonably similar, but there are big enough differences that it would be difficult to write compatibility wrappers that would allow code expecting Vuex 4 to run on Pinia. Instead, we would use Vuex 4 and Pinia side by side for a while, with new code using Pinia, and old code being migrated from Vuex 4 to Pinia over time. This theoretically means that both libraries could be loaded on the same page, which would be (slightly) wasteful; but I don't think that it'll happen much in practice, because the features that currently use Vuex tend to be ones that take over the entire page. To install Pinia in MediaWiki, we would probably want to use `pinia.iife.prod.js` / `pinia.iife.js` and wrap them so that `VueDemi` is aliased to `require( 'vue' )`. Alternatively, we could use `pinia.prod.cjs`, but then we would have to set up a module alias for `vue-demi` to redirect to `vue`, and we would have to make `@vue/devtools-api` available (in the iife versions, that package is inlined). ==== Pending security review {T308495}

=== Background **[[https://pinia.vuejs.org/|Pinia]] is the successor to Vuex**. It promises to be lighter weight than Vuex (6KB for Pinia 2.0.13, 15KB for Vuex 4.0.2) and to support TypeScript better. The main challenge we'd have to address in order to use Pinia is that Pinia is mostly compatible with Vuex 4We could not immediately replace Vuex 4 with Pinia, because Pinia isn't fully backwards compatible with Vuex 4. The APIs are reasonably similar, but there are big enough differences that it would be difficult to write compatibility wrappers that would allow code expecting Vuex 4 to run on Pinia. Instead, we would use Vuex 4 and Pinia side by side for a while, with new code using Pinia, but not entirelyand old code being migrated from Vuex 4 to Pinia over time. The API for creating a store is different (weThis theoretically means that both libraries could probably add a compatibility wrapper for this)be loaded on the same page, and mutations don't exist in Pinia.which would be (slightly) wasteful; Modifying code written for Vuex 4 suchbut I don't think that it would work with both Vuex 4 and Pinia'll happen much in practice, or adding compatibility wrappers so that Vuex 4 code works with Pinia (which would be required for a smooth migration from Vuex to Pinia) may or may not be easybecause the features that currently use Vuex tend to be ones that take over the entire page. To install Pinia in MediaWiki, we would probably want to use `pinia.iife.prod.js` / `pinia.iife.js` and wrap them so that `VueDemi` is aliased to `require( 'vue' )`. Alternatively, we could use `pinia.prod.cjs`, but then we would have to set up a module alias for `vue-demi` to redirect to `vue`, and we would have to make `@vue/devtools-api` available (in the iife versions, that package is inlined). ==== Pending security review {T308495}