-
Notifications
You must be signed in to change notification settings - Fork 119
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
any support for webpack-4 or webpack-5 #125
Comments
?Were you able to get this working correctly? Even with Webpack-5? |
Working fine for me on Webpack 5, Node 14.. |
@perry-mitchell how did you resolve img path in pug? index.js webpack.config.js |
@perry-mitchell |
Sorry, but simple-pug-loader not resolve Webpack Aliases. It doesn't work for me, e.g.:
where Here is alternative pug-loader, 100% compatible with original pugs/pug-loader, but work with Webpack 5 and Pug 3 , support webpack aliases and is many time faster. |
I just did because after recent fixes by @webdiscus, |
I've been trying to utilize the loader for the pug+webpack boilerplate,
but had problems to do so, even after extensive reading of
https://webpack.js.org/loaders/
and all documentation provided by pugjs/pug-loader.
there are bi-directional redirections of the help sections from pug-loader to webpack/loaders,
I find the examples under the documentation sections - partial at best,
There are nice articles how to "tie-in" all the pieces together,
for example: https://extri.co/2017/05/23/using-htmlwebpackplugin-and-pug/
and https://itnext.io/webpack-4-write-pug-templates-c24e5ea07317,
and the nice github-issue - #97
Looks like webpack is the de facto standard of the current candlers and I suspect that providing official full covering documentation may be very beneficial for on-boarding pug and webpack newcomers.
The text was updated successfully, but these errors were encountered: