"Loading chunk" error on some MDN pages

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry goes blank a couple hundred ms after loading, with these errors in devtools:

Content Security Policy: Couldn’t process unknown directive ‘script-src-elem’
Loading failed for the <script> with source “https://developer.mozilla.org/static/js/6.397539b0.chunk.js”. FinalizationRegistry:1:1
ChunkLoadError: Loading chunk 6 failed.
(error: https://developer.mozilla.org/static/js/6.397539b0.chunk.js)
    Webpack 57
react-dom.production.min.js:216:199
Uncaught ChunkLoadError: Loading chunk 6 failed.
(error: https://developer.mozilla.org/static/js/6.397539b0.chunk.js)
    Webpack 57
bootstrap:172:17

[kg]

StatusCode        : 200
StatusDescription : OK
Content           : (this.webpackJsonpclient=this.webpackJsonpclient||[]).push([[6],{131:function(e,t,n){"use
                    strict";n.r(t),n.d(t,"default",(function(){return H}));var
                    r=n(6),a=n(3),s=n(0),c=n(1),o=n.n(c),i=n(2),l=o.a.c...
RawContent        : HTTP/1.1 200 OK
                    Connection: keep-alive
                    X-Frame-Options: DENY
                    X-XSS-Protection: 1; mode=block
                    X-Content-Type-Options: nosniff

Seems like it was a transient failure that got cached. I think MDN’s frontend might benefit from having a way to detect that a chunk load failed like this and either show an error message or re-try it somehow - I got a completely blank page and had to dig through the devtools logs to figure out which error messages were relevant + stuck across multiple loads.

[caugner]

Maybe this happens when

1. an MDN page is loaded immediately before our CDN is invalidated, and
2. that outdated page loads a chunk that no longer exists.