10 minutes
| Peer dependency on Paragon in @openedx/frontend-build?
| Adam Stankiewicz
| Context: There is some forward-looking intent to “go build-less” in JS libraries, where dist would no longer exist. There are several code paths within ParagonWebpackPlugin that expect dist to exist. ParagonWebpackPlugin also depends on a specific file, theme-urls.json within the installed @openedx/paragon.
[question/concern] How do we prevent instances that deploy to production from master from causing a regression when upgrading to a version of paragon/brand that no longer contains dist (e.g., buildless) or theme-urls.json (e.g., renamed)? There could be risk in not properly catching an upgrade of @openedx/paragon (for example) that results in deploying an MFE with no CSS, as it would not throw any errors during build and likely not trigger alerts during monitoring, resulting in a largely unusable app without styles. Notes: |