-
Notifications
You must be signed in to change notification settings - Fork 42
==> NEW REPOSITORY <== (don't open issues here) #38
Comments
Nice! Webpack 2 support? |
Webpack 2 + WOFF2 |
Sweet - this is my last blocker for upgrading to Webpack 2, will hopefully give it a try soon |
@jeerbl Let me know if you want to move webfonts-loader below webpack-contrib org. We set it up to avoid situations like here. |
Yep good idea! How do we proceed ? |
@d3viant0ne Just getting you in the loop. webfonts-loader took over fontgen-loader development and would be an excellent candidate for inclusion to webpack-contrib. Let me know what you think. 👍 |
Right out of the gate, there are going to be licensing issues that will need to go through JSFoundation legal before anything goes anywhere. Original repo is MIT, the copy which is not a fork has been relicensed as Unlicense. It's a legal mess that I am inclined to just avoid entirely. |
What would you need as a licence? The original one is MIT therefore we just need to provide attributation back to the creator, right? |
Would also love to get some feedback on https://github.com/jantimon/iconfont-webpack-plugin it uses the caching and watching of webpack instead of globs or custom configs |
Hi guys,
This repository has not been updated since March 2016 so I decided to take it over at jeerbl/webfonts-loader so that I can fix the issues that still occur. I had to change the package name on npm to
webfonts-loader
.Feel free to use the new repository for any issues. If you want to collaborate on this, get in touch with me.
Cheers
Jerome
The text was updated successfully, but these errors were encountered: