Currently, the webpack rules create javascript which looks for fonts in a relative path like:
src: url(\'assets/fonts/UQM-3DOMenuLabels.ttf\')
I currently hand-edit after building to hardcode those paths to include the full path, like so:
src: url(\'https://pistolshrimpgames.com/planets/assets/fonts/UQM-3DOMenuLabels.ttf\')
This seems unnecessary, but I get different results in different web browsers using various flavors of relative paths when looking for fonts in a relative path.
How do we, either:
Create a relative path which plays nice on all browsers for font loading on that server? (might be beyond the scope of this issue and a server config issue - help welcome here)
Create some webpack build target which knows how to do those edits for me, to make build & deploy less painful?
Currently, the webpack rules create javascript which looks for fonts in a relative path like:
src: url(\'assets/fonts/UQM-3DOMenuLabels.ttf\')
I currently hand-edit after building to hardcode those paths to include the full path, like so:
src: url(\'https://pistolshrimpgames.com/planets/assets/fonts/UQM-3DOMenuLabels.ttf\')
This seems unnecessary, but I get different results in different web browsers using various flavors of relative paths when looking for fonts in a relative path. How do we, either: