Nulo/gitea
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity

Fix webpack chunk loading with STATIC_URL_PREFIX (#11526) (#11542)

Browse source 
Previously, we had only set __webpack_public_path__ to a path which
caused webpack chunks to be loaded from the current origin which is
incorrect when STATIC_URL_PREFIX points to another origin.

This should fix the issue curretnly seen on gitea.com.
This commit is contained in:
silverwind 2020-05-22 21:18:44 +02:00 committed by GitHub
parent d131d53cbb
commit 573a9c6228
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
web_src/js/publicpath.js
View file

@ -1,7 +1,10 @@
// This sets up webpack's chunk loading to load resources from the 'public' // This sets up the URL prefix used in webpack's chunk loading.
// directory. This file must be imported before any lazy-loading is being attempted. // This file must be imported before any lazy-loading is being attempted.
const {StaticUrlPrefix} = window.config;
if (document.currentScript && document.currentScript.src) { if (StaticUrlPrefix) {
__webpack_public_path__ = StaticUrlPrefix.endsWith('/') ? StaticUrlPrefix : `${StaticUrlPrefix}/`;
} else if (document.currentScript && document.currentScript.src) {
const url = new URL(document.currentScript.src); const url = new URL(document.currentScript.src);
__webpack_public_path__ = url.pathname.replace(/\/[^/]*?\/[^/]*?$/, '/'); __webpack_public_path__ = url.pathname.replace(/\/[^/]*?\/[^/]*?$/, '/');
} else { } else {