-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Configuring an *.html module loader beats down template variables #540
Comments
Yes that's expected behaviour - you can find out more about that in the FAQ :) |
Thank you. Could you please give me a little bit more help? Can I somehow specify the fallback loader in "template" config option explicitly? Something like
Of course, installing https://www.npmjs.com/package/underscore-loader dependency does the trick, but is it possible to use your built-in loader instead? Also, for some reason, this solution refused to work properly until I changed the template path to "./templates/base.html". See diff |
|
This is very helpful, thank you |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Registering a default loader for *.html modules in WebPack breaks the variables resolution in template. For example:
In result, the variables are left unresolved:
Changing the test expression to something more detailed fixes the problem:
I've created a minimal repository demonstrating the problem https://github.com/enepomnyaschih/html-plugin-bug
Just run:
And check public/index.html file.
Is that expected behaviour?
The text was updated successfully, but these errors were encountered: