Closed mochiya98 closed 3 years ago
IIUC the problem is that findRegularFontFiles
finds font files that get preferred over the correct ExtractText ones?
If that's true, I think we could be a bit more explicit with a fix and say something like
// Prefer the ExtractTextPlugin version of any assets we find
const regularWithExtractRemoved = _.differenceBy(regular, extract, 'asset')
return _.uniqBy(regularWithExtractRemoved.concat(extract), 'asset')
Hello @patrickhulce,
Thanks for the great work on this plugin!
I'm currently experiencing a bug where some glyphs aren't bundled in final font files when they're present in several font variations (I'm trying to minify FontAwesome).
I'm building with Webpack 5 & v3.0.1 of your plugin.
With master branch code, glyphs are added in fa-light-XXX files, but not in fa-solid, fa-regular etc. files.
With @mochiya98's fix or yours, glyphs are properly added to each FontAwesome variation files.
Could you push this fix on master?
Thanks :)
Ah, sure @Moustachos I'll push that later today 👍
Note
It's already fixed partially.
refs: #13
Why does it happen?
when using ExtractTextPlugin,
compilation.modules
is changed.without ExtractTextPlugin:
with ExtractTextPlugin:
What problem will this cause?
with ExtractTextPlugin:
Is it solved completely in the current version(2.0.2) ?
no.
Problems will occur in the following cases:
uh, maybe these problems will be solved in the following ways:
...isn't it?