To solve these issues:

• MathJax 3 can be broken into separate pieces:
  • Input and output jax
  • Adaptors and handlers
  • TEX extensions
  • Third-party extensions
• Each is webpacked separately but shares common code.
• They can be mixed and matched as in MathJax 2.
• There is a loader component that loads these (asyncronously) in the right order.
• There is a startup component that can create typeset and conversion functions based on the pieces loaded.