As discussed on Slack, we currently have no easy way of knowing if SRI data is missing for files. This adds logic to our SRI loading, so that if SRI data is missing for js/css files when a request comes in for a library or a version of a libary, we will log an error in Sentry & console.
This doesn't make the request fail, the existing clean error handling will allow SRI to be blank etc, but it does mean we will see Sentry errors for any missing SRI data.
CI is currently failing due to an unrelated error -- the generated package data is missing the autoupdate field for packages, which the test suite expects to exist.
Type of Change
What issue does this relate to?
N/A
What should this PR do?
As discussed on Slack, we currently have no easy way of knowing if SRI data is missing for files. This adds logic to our SRI loading, so that if SRI data is missing for js/css files when a request comes in for a library or a version of a libary, we will log an error in Sentry & console.
This doesn't make the request fail, the existing clean error handling will allow SRI to be blank etc, but it does mean we will see Sentry errors for any missing SRI data.
What are the acceptance criteria?
CI passes, logic looks correct.