Can you add an e2e test for this PR?

@hansl working on it.

What's the status for those tests failing?

solution itself is not okay. I am suspicious of a bug in webpack resolver, but not sure. I'll try to find a solution for this elsewhere in paths-plugin.ts file since previous regex was just fine.

FWIW, the solution I've been using to get the paths to work in my non-angular-cli webpack configuration prior to attempting to integrate @ngtools/webpack as the typescript loader was to use ts.nodeModuleNameResolver against the request and use the result of that (if any) as the new request. So far, it's worked with all the scenarios I've tried it with (including the ones I mentioned in #3441), I'm just not entirely sure if most optimal way of doing so.

@chrisfitz thanks for the tip! @hansl can you please check again?

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}