Support Webpack defined modules about pug-loader

[webdiscus]

@m10

In v2.6.4 is enabled supports for resolve.modules options defined in webpack config.

P.S. all performance optimised pre-settings of Webpack resolver was removed. Now you can change every options of Webpack resolver.

[webdiscus]

@m10

you can use Webpack aliases, e.g.:

  resolve: {
    alias: {
      Views: path.join(__dirname, 'src/views/'),
      Images: path.join(__dirname, 'src/assets/images/'),
      Fonts: path.join(__dirname, 'src/assets/fonts/'),
      Styles: path.join(__dirname, 'src/assets/styles/'),
      Scripts: path.join(__dirname, 'src/assets/scripts/'),
    },
  },

Usage of aliases in Pug

extends Views/layouts/default
include Views/mixins
img(src=require('Images/image.jpg'))
- const data = require('Scripts/data.json')

Usage of aliases in SCSS

@font-face {
  font-family: 'OpenSans';
  src:
    url('Fonts/OpenSans/open-sans-regular.svg') format('svg'),
    url('Fonts/OpenSans/open-sans-regular.woff2') format('woff2');
  font-style: normal;
}

.header {
  background-image: url('Images/image.jpg');
}

P.S. I'm not sure if supporting resolve.modules is important. I have set this enhancement to a low priority and do it in my free time.

[m10]

thanks for taking the time to look into it. I appreciate your effort!

I know that one can use aliases too but when adding/removing folders one would have to add/remove aliases too..
It is more dynamic and intuitive with modules.

Just IMHO: Dependency resolution should work consistently across Webpack. It's what users expect. Any difference should at least be documented.

We have legacy projects where this is used. Migrating them to this loader would be more difficult without this support.
On new projects it would be possible to work around this, even though it would be nice to keep the workflow

[webdiscus]

@m10

from readme > features:

...

• resolves alias from webpack resolve.alias
• resolves alias from tsconfig.json compilerOptions.paths, requires tsconfig-paths-webpack-plugin

...
and here are many examples of resolving
Currently is supported what is documented ;-)

Many of my and many client projects have never never used the resolve.module.
If support is required now, then well, I will do it.