Editor in File Manager throwing HTTP 404 errors

[d19dotca]

I was using Safari 15.1 on macOS 12.1 and was having some trouble loading any files in the editor via the Cloudron File Manager. It eventually resolves itself, but I noticed this in the web console, wanted to pass it along in case this is a defect (seems like it might be).

[Warning] pascalprecht.translate.$translateSanitization: No sanitization strategy has been configured. This can have serious security implications. See http://angular-translate.github.io/docs/#/guide/19_security for details. (angular-translate.min.js, line 6)
[Error] Failed to load resource: the server responded with a status of 404 () (showdown.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (angular-cookies.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (true, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (loader.js.map, line 0)
[Log] Running filemanager version  – "7.0.4" (filemanager.js, line 1017)
[Error] Failed to load resource: the server responded with a status of 404 () (editor.main.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (editor.main.nls.js.map, line 0)
[Error] Refused to load https://<hostname>/3rdparty/vs/base/worker/workerMain.js#editorWorkerService because it appears in neither the child-src directive nor the default-src directive of the Content Security Policy.
[Warning] Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/microsoft/monaco-editor#faq (editor.main.js, line 68)
[Warning] The operation is insecure. (editor.main.js, line 68)
[Error] Refused to load https://<hostname>/3rdparty/vs/base/worker/workerMain.js#json because it appears in neither the child-src directive nor the default-src directive of the Content Security Policy.
[Warning] The operation is insecure. (editor.main.js, line 68)

[nebulon]

@d19dotca unfortunately I do not have a macOS device to test this with safari and it seems chromium and firefox do not hit this issue.