It doesn’t work. Obviously because there is no scss, or fonts directory. Am I expected to replace those paths with the path to bower_components/font-awesome/sass/font-awesome.sass? Doesn’t seem right to have to do that.
I love sage and all, but it seems like the developers may have overcomplicated something which should be simple. This is a question I’ve seen pop up all over the internet, and usually the accepted response is a link to the thread I included at the top.
It’s literally taken me hours to try get font awesome installed. What is the purpose of bower in 2016 anyway? Can’t it be replaced with npm seen as all the bower packages are also on npm? Or better still move over to webpack A quote from a engineer at Spotify:
In almost all cases, it’s more appropriate to use Browserify and npm over Bower. It is simply a better packaging solution for front-end apps than Bower is. At Spotify, we use npm to package entire web modules (html, css, js) and it works very well.
I appreciate any help on clearing up my confusion on getting font awesome to work.
I also should have installed using: bower install fontawesome --save instead of save-dev (I have no idea why I installed like that in the firstplace, I blame sleep).
into "dependencies" section of sage/assets/manifest.json
Major downside of this approach is slower build process, especially when there are lots of bower packages (I haven’t tested it yet on a real projects, don’t know how much slower).
Upd.: I would not recommend using this method, because it requires very specific bower packages with .scss / .css entry point and font files being strictly in the fonts directory (but not it’s sub-folders)
I was also adding font awesome for one of my projects, but found out their service https://fortawesome.com where you add your own icon kit (so you don;t load all the icon library) , add your own icons or logos and load it via CDN, was super easy.
I ran the command you shared above but Chrome Console is saying it can’t locate the font files themselves. Should the above command include them automatically? Or do I need to manually add them somehow?
@s3w47m88 TBH I can’t quite recall, I’m on Sage 9 now which uses different build tools. Have a go and see if it works, if not you may need to add manual refs in somewhere.