Sam Chen

I just checked the source code https://github.com/webpack/webpack/blob/2a58ce7883b42e1ebcfde617ec4a27c7feb035e6/lib/FileSystemInfo.js#L1997, capture group is required to work. So I think the confusing part is why not just use a normal regexp to match paths...

@SystemParadox I've tried to [file a patch](https://github.com/webpack/webpack/pull/15969) so we don't need the capture group. But unfortunately this seems to be a breaking change. Maybe they can fix it in webpack...

I've merged that pull request but will keep this issue open since it's valid concern in my opinion.

Actually we did have a guide here https://webpack.js.org/configuration/configuration-languages/#typescript, so maybe we can just add a link to that in this page?

I'll see if I can document it.

Unfortunately I can't make the option work as I expected, if anyone are interested in documenting it, please go ahead. And here's the related section https://webpack.js.org/api/module-methods/#dynamic-expressions-in-import

Webpack is a bundler, so it's likely to bundle any files you have unless you tell it not to :) Hence I think it's not necessary to explain it? Otherwise...

@ArielGueta You can send a PR to improve it https://github.com/webpack/webpack.js.org/blob/master/src/content/concepts/targets.md.

Unfortunately I'm not able to reproduce with the configuration you provided:  Could you share more? It would be much better if you can provide...

I'm afraid these's no one-size-fits-all solution as the documents don't share a common pattern. E.g., 1. `/configuration/module/#modulegenerator` 2. `/configuration/module/#rulelayer` This pull request would work only for the first pattern. And...