Closed cmastelaro closed 2 years ago
After builds the code trying to load fonts from http://localhost:4000/js/fonts/Roboto-LightItalic.2eeb30eb.ttf
Same issue here, when i run quasar build, the compiler put font in /fonts folder and try to load on /js/fonts, something is wrong when translating url after build. Is it a webpack missing configuration inside a quasar.conf.js?
Probably the build command somehow differs. This example uses vue-cli-service build
in its package.json
. The result is in this repo: https://github.com/vagran/dxf-viewer-example It has fonts
directory on top level.
Some weird things happening with quasar compilations. I fixed the problem by go out of from "import from" to const var like this:
const mainFont = '/fonts/Roboto-LightItalic.ttf'
const aux1Font = '/fonts/NotoSansDisplay-SemiCondensedLightItalic.ttf'
const aux2Font = '/fonts/HanaMinA.ttf'
const aux3Font = '/fonts/NanumGothic-Regular.ttf'
and moving font files from assets/fonts folder to public/fonts.
Should be related to webpack config. See here: https://chriscourses.com/blog/loading-fonts-webpack Probably, when building by vue-cli-service these rules already applied by default. Another way may be specifying file loader inline: https://webpack.js.org/concepts/loaders/#inline
The fonts used to worker loader work's nicely on dev mode, but when we make quasar build the fonts are not imported.
Getting error Unsupported OpenType signature
i don't have any clue in what i'm doing wrong
PS: using quasar.conf.js