-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
intention
I have a Fork with some UI adjustments to show uuids that I want to host in a subfolder.
expected behaviour
The weppack configuration with a different Subfolder is used.
actual behaviour
The Configuration fixed not all of the links. Some requests still use "/" instead of the provided output.publicPath.
reproduce
- added
output.publicPath: '/my/subfolder/'
to webpack.config.prod.js npm run build
docker buildx build
the nginx image with webapp- integrate in my Environment
Now it mostly works but some ressources are still not found due to a wrong requested path (ignoring my base path according to browser dev tools).
- using
grep -r "base href"
i found this:
./dist/index.html: <base href="/" target="_blank"/>
- replaced the base href path in
./dist/index.html
"/" with "/my/subfolder/"
Since this base path is used in ./src/template.html I assume this is a second place where I'd have to set the subfolder:
./src/template.html: <base href="/" target="_blank"/>
Since this is the same configuration done in two places I want to ask: Is this intended behaviour?
Metadata
Metadata
Assignees
Labels
No labels