Update MediaWiki and Codex to Vue 3.5
Open, Needs TriagePublic1 Estimated Story Points
Actions

Assigned To

Authored By

	simon04
	Sep 5 2024, 5:20 PM

Description

Vue 3.5 has been released in September 2024. Citing a significant performance improvement from the official blog post: https://blog.vuejs.org/posts/vue-3-5

In 3.5, Vue's reactivity system has undergone another major refactor that achieves better performance and significantly improved memory usage (-56%) with no behavior changes.

Follow-up to T364789.

Details

	Subject	Repo	Branch	Lines +/-
	build: Update Vue to 3.5.13	design/codex	main	+84 -95
	Update Vue to 3.5.13	mediawiki/core	master	+7 K -6 K

Customize query in gerrit

Related Objects

Mentioned Here: T364789: Update MediaWiki and Codex to Vue 3.4

Event Timeline

simon04 created this task.Sep 5 2024, 5:20 PM

Restricted Application added a project: Design-System-Team. · View Herald TranscriptSep 5 2024, 5:20 PM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Thanks @simon04. We're not in a rush to update but we will try to slot this in to an upcoming sprint.

CCiufo-WMF triaged this task as Low priority.Sep 5 2024, 5:49 PM

CCiufo-WMF raised the priority of this task from Low to High.Nov 18 2024, 9:34 PM

CCiufo-WMF raised the priority of this task from High to Needs Triage.

CCiufo-WMF moved this task from Needs Refinement to Housekeeping on the Design-System-Team board.

Volker_E awarded a token.Nov 26 2024, 11:02 PM

AnneT set the point value for this task to 1.Mon, Dec 9, 6:27 PM

AnneT moved this task from Housekeeping to DST-Sprint-38 (2024-12-09 to 2024-12-20) on the Design-System-Team board.

AnneT edited projects, added Design-System-Team (DST-Sprint-38 (2024-12-09 to 2024-12-20)); removed Design-System-Team.

Catrope claimed this task.Mon, Dec 16, 8:37 PM

I tried upgrading Codex to Vue 3.5, but unfortunately there is a bug in Vue 3.5 (or maybe in vue-tsc) that breaks TypeScript checks for components that use expose. We can't upgrade until that bug is resolved or unless we decide to (temporarily?) not use expose. (To be fair, it provides a bit of a false sense of security currently, because Option API components expose everything by default; so our components with no public API currently expose more things than the ones with a defined public API.)