fix(@ngtools/webpack): prevent relative request path mapping#9787
fix(@ngtools/webpack): prevent relative request path mapping#9787clydin merged 1 commit intoangular:masterfrom
Conversation
| const originalRequest = request.request.trim(); | ||
|
|
||
| // Relative requests are not mapped | ||
| if (originalRequest.startsWith('.')) { |
ed625cd to
e63b8ca
Compare
|
@clydin @hansl @filipesilva why has been added this limitation in the paths mapping? It sounds like a problem to me when you develop specially a component library. For example in my project I have a stucture like: MY-PROJECT Now if I want point my lib component from my demo app (without publish or at least build the library) what I am currently doing is to relatively point from the tsconfig to my lib.(Otherwise it will get the node_modules version of my library). Using the tsconfig to map a relative lib has a lot of advantages during the development; in particular the watcher that will keep to check if I modify something in my lib and will let me test it in my demo app. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes #9727