-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fonts are not being included in second and consecutive builds #517
Comments
Also an issue here - using
And all woff/otf files and some svgs don't show up on the page. |
Hello, I'm also having this issue, did you find a workaround ? Thanks |
I solved the problem like this: new HardSourceWebpackPlugin(),
new HardSourceWebpackPlugin.ExcludeModulePlugin([
{
test: /file-loader/,
},
{
test: /webfonts-loader/,
},
]), No caching fonts, no problem ) |
@attikos's workaround works well but surely this decreases the speed of the build (and certainly increases developer time since I had to come look for this bug) |
I have a question, can i use :
|
As the RegExp is applied to the whole request path of the module and module name is also a component of request path, I think the config you suggested above is available. For details, debug here on yourself. ExcludeModulePlugin.js |
Expected Behavior
Fonts are included in second and consecutive builds, just like the first run.
Actual Behavior
Fonts are not being included in second and consecutive builds.
Is an error being thrown?
No.
Steps to Reproduce
Using
file-loader
forttf
andwoff
fonts.Using
postcss-loader
,css-loader
andextract-css-chunks-webpack-plugin/loader
forscss
files.Using
hard-source-webpack-plugin
as following:Operating System, Node, and NPM dependency versions
Similar Issues
#357
#378
The text was updated successfully, but these errors were encountered: