Failed to build when webpack alias for asset is an array of paths instead of a single path about pug-loader HOT 5 CLOSED

Awesome! THe workaround for not using variables in the require expression is simply to prepare utility data structures. Such as:

- const statusIcons = { draft: require('images/status/draft.png'), reject: require('images/status/reject.png'), review: require('images/status/review.png'), approve: require('images/status/review.png') };

from pug-loader.

Thanks for adding it to the "in development" milestone. :) I hope I will not have to wait for long as I'm slightly blocked, but not too worry too much :)

from pug-loader.

hallo @Rush

thank you for very important issue. I have enhanced the resolving of alias for array.

You can see possible usage cases in the fixture and resolve.alias for compile method.

⚠️ Limitation for compile method and alias as an array

Usage of a variable in request don't work if alias is an array:

resolve: {
  alias: {
     Images: ['/path_1/', '/path_2/'],     
  }
}

- var basename = 'logo';
img(src=require('Images/' + basename + '-c1.jpeg')) <-- does not work

img(src=require('Images/logo.jpeg')) <-- works

This is limitation of webpack compiler self, webpack don't recognize an asset request contained a variable. But the webpack resolver resolve this assets correct. This limitation does not affect the render and html methods.

New version is 1.7.1

from pug-loader.

Awesome! The workaround for not using variables in the require expression is simply to prepare utility data structures. Such as:

- const statusIcons = { draft: require('images/status/draft.png'), reject: require('images/status/reject.png'), review: require('images/status/review.png'), approve: require('images/status/review.png') };

Thanks, it works too :-)

from pug-loader.

Fixed, works great now. Thank you!

from pug-loader.