Fixes #14. I tried various things, and this combo was the one that worked best for me. A few things to note:
The planets/ path from which the tool is served in production is now present in the config. If the path changes, the config needs to change as well. Dev mode still uses root.
The production build now creates the files in dist/planets/ instead of dist/.
Dropping ttf-loader (probably) means that the fonts can't be used directly in JavaScript (see usage examples), but that's likely not going to be an issue. 🙂
I didn't remove ttf-loader from package.json, since it would've resulted in a big chunk of unrelated changes in package-lock.json due to Node/NPM version differences.
Tested in dev and production modes with Chrome.
If there are still some issues with the font file serving in production, please let me know.
Fixes #14. I tried various things, and this combo was the one that worked best for me. A few things to note:
planets/path from which the tool is served in production is now present in the config. If the path changes, the config needs to change as well. Dev mode still uses root.dist/planets/instead ofdist/.ttf-loader(probably) means that the fonts can't be used directly in JavaScript (see usage examples), but that's likely not going to be an issue. 🙂ttf-loaderfrom package.json, since it would've resulted in a big chunk of unrelated changes in package-lock.json due to Node/NPM version differences.Tested in dev and production modes with Chrome.
If there are still some issues with the font file serving in production, please let me know.