# Upgrading Mathjax to version 4

**URL:** <https://meta.discourse.org/t/upgrading-mathjax-to-version-4/392669>\
**Category:** Development\
**Tags:** math\
**Created:** [November 23, 2025, 5:57pm UTC](https://meta.discourse.org/t/upgrading-mathjax-to-version-4/392669 "2025-11-23T17:57:05Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)\
**Post date:** [January 3, 2026, 9:11am UTC](https://meta.discourse.org/t/upgrading-mathjax-to-version-4/392669/20 "2026-01-03T09:11:21Z")

</div>

I understand that the discourse-math plugin relies on the separate MathJax/KaTeX asset gem rather than vendoring those libraries directly, which keeps the plugin lightweight and allows the math libraries to be updated independently.

I’d like to help validate this ahead of the first production release by doing some real-world testing. My initial thought was to spin up a separate, disposable instance and enable the plugin there to test math-heavy content, asset loading via the standard pipeline, CSP behaviour, and performance.

Before doing so, I wanted to ask what the recommended environment is at this stage - whether early testing in a production-like setup l is appropriate, or whether you’d prefer this to be done using a development environment until the first production release.

I’m very happy to test in whichever way is most useful and to report any issues or edge cases I encounter upstream. I can’t commit to a fixed testing schedule due to university commitments, but I’m happy to do best-effort testing when time allows, and I’m likely to have significantly more availability after 6 June.

---

_[View the full topic](https://meta.discourse.org/t/upgrading-mathjax-to-version-4/392669)._