Content Hash different for same font file
We are on the verge of deploying a new site with this great font gen loader and we exposed a bug that may be this loader's issue or something up with webfonts-generator. Showed up during our deploy process that runs our webpack build on several servers, with our assets behind an ELB managing load.

Same version of node, shrinkwrapped npm, same exact npm list, same branch, yet we get different hashes on the woff2/woff font files, while SVG generation is identical every time. If you're running just one server this isn't an issue, but with several it becomes a blocker as all the CSS files that point to that font now have a different hash as well.

Quick fix is to force a manual cache buster like so: `"fileName": "[fontname].1.[ext]"` and just update the number manually whenever the file gets updated. Anyway, just wanted to put this on the map in case anyone else is suffering from the same issue.