Break up Capa XModule JS bundle

Description

Now that XBlock assets are served up in by the CDN and in a nicely cached way, we can look at breaking up the giant ball of JavaScript that goes into CapaModule. This would allow us to omit things like the circuit schematic input type's JavaScript for most page loads. This would require that Capa be smart enough to return a subset of its assets as part of the fragment, depending on which input and response types are present.

I'm not sure if it makes sense to do this until HTTP/2 rolls out. On the one hand, there is an overhead for multiple requests. On the other hand, the actual number of problem types used in practice is pretty small, so it might not matter.

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Unassigned

Reporter

David Ormsbee

Labels

None

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Story Points

5

Priority

Unset
Configure