Improve performance

[RichDom2185]

Our lighthouse score is really bad:

Not to mention, our main bundle size as-is is already 15.7MB, which can take forever to load; we will hit the current 16MB limit in the near future (in fact, we already did simply by upgrading dependencies – see the CI failure on #2498).

We should try to do code-splitting or investigate some other way to improve the performance.

[chownces]

After #2507, here is the breakdown of our bundles (via yarn analyze).

More can be done to reduce the bundle size arising from js-slang dependencies, which are unused most of the time

• ts-morph (for typed source variant) - 4.07MB
• alt-ergo (for infinite loop detection) - 1.61MB
• results in our main.js bundle being 10.76MB

Lighthouse scores are still bad (further investigation needed):

[RichDom2185]

After #2507, here is the breakdown of our bundles (via yarn analyze).

What's the use of typescript.js? At first glance, it seems like this is more of a dev dependency than a prod one.

[chownces]

After #2507, here is the breakdown of our bundles (via yarn analyze).

What's the use of typescript.js? At first glance, it seems like this is more of a dev dependency than a prod one.

It should be used by the typed Source variant, as part of ts-morph. So it is a dependency for js-slang

[RichDom2185]

It should be used by the typed Source variant, as part of ts-morph. So it is a dependency for js-slang

Hmmm, in that case, perhaps we can investigate if we can load the required dependencies dynamically depending on the selected language; something like the TypeScript Playground maybe?