It’s me again, another question (sorry).
I’m using firstname.lastname@example.org to bundle the frontend app. One of the dependencies is email@example.com. This is working fine when using steal to load everything.
It had been working fine in production too, but then I decided that the node_modules directory shouldn’t really be included in the production container. So it turns out that the font-awesome fonts directory is not being added to the production bundle and so the fonts cannot load when the node_modules directory is not present in the container.
My colleague suggested using the bundleAssets option with steal-tools. Once I added this, then I see that steal-tools is trying to add the fonts (i think). I see the following warning.
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, lstat '/opt/wsp/fonts/glyphicons-halflings-regular.eot'
In the code, I am importing the font-awesome css file like this
This file references the fonts like this:
src: url('../fonts/fontawesome-webfont.eot?#iefix&v=4.7.0') format('embedded-opentype'), url('../fonts/fontawesome-webfont.woff2?v=4.7.0') format('woff2'), url('../fonts/fontawesome-webfont.woff?v=4.7.0') format('woff'), url('../fonts/fontawesome-webfont.ttf?v=4.7.0') format('truetype'), url('../fonts/fontawesome-webfont.svg?v=4.7.0#fontawesomeregular') format('svg');
The fonts directory is installed in
Any ideas? I can work around this by mounting the node_modules/font-awesome/fonts directory in the production container, but this seems wrong and I would like to understand if this is a problem or not.