You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that getPathsToTry does not resolve modules starts with the path separator of system where it runs, it makes difference in resolution between Windows and Linux. So tsconfig-paths-webpack-plugin does not try to resolve modules starting with / on Linux whereas it does on Windows.
(see dividab/tsconfig-paths-webpack-plugin#87 (comment))
I presume this is intentional, then what is the reason?
I don't know recommended arrangements for image modules in css, but image modules kinda oftentimes start with / in projects I'm working on, which I don't see as an exceptional or a special usage in css url function.
Some people like me would need to define aliases starting with / in webpack config as well if this module is not gonna change this issue.
The text was updated successfully, but these errors were encountered:
I came from this issue: dividab/tsconfig-paths-webpack-plugin#87
I found that
getPathsToTry
does not resolve modules starts with the path separator of system where it runs, it makes difference in resolution between Windows and Linux. So tsconfig-paths-webpack-plugin does not try to resolve modules starting with/
on Linux whereas it does on Windows.(see dividab/tsconfig-paths-webpack-plugin#87 (comment))
I presume this is intentional, then what is the reason?
I don't know recommended arrangements for image modules in css, but image modules kinda oftentimes start with
/
in projects I'm working on, which I don't see as an exceptional or a special usage in css url function.Some people like me would need to define aliases starting with
/
in webpack config as well if this module is not gonna change this issue.The text was updated successfully, but these errors were encountered: