Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

function getPathsToTry does not try to resolve modules starting with a path separator #194

Closed
cdpark0530 opened this issue Mar 14, 2022 · 2 comments

Comments

@cdpark0530
Copy link

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.

@jonaskello
Copy link
Member

jonaskello commented Mar 14, 2022

I think this may be solved by #180 which was merged yesterday and released in 3.14.0.

Could you try 3.14.0 and see if that solves the problem?

@cdpark0530
Copy link
Author

@jonaskello
It works perfectly. I really appreciate your job!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants