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
relative filepaths breaking #48
Comments
Can you debug what |
Thanks for taking a look. This is the value of the file var when I get the error.
|
Hm. Seems like we need to use different way to get file path. @davidjbradshaw because this issue is reproduced only for you, can you try some methods locally? Or add new test? |
Happy to try something locally. Not sure I have a deep enough understanding of webpack and postcss to write a test case. |
@davidjbradshaw don’t worry, I am not a weback user at all, but developing this module :D. |
Main problem is really big webpack API complexity. Taking a file name is a common procedure for loader, but I can’t find good way to do it :(. |
@davidjbradshaw can you debug what will be in |
Can you point me at where the break point should be for that? |
@davidjbradshaw same line 7 |
Sorry for the slow reply. This is what I get for this.resourcePath.
|
Awesome. I will replace a way to get current file path. Sorry, new release could be released only in Sunday (I am traveling between cities). |
Thanks and next week is fantastic. |
Done 3c9b715 |
Released in 0.8.1. |
still have the same problem using |
I'm trying to use the postcss-inline-svg plugin via the postcss-loader in webpack to inline an SVG file with the following line of code.
However, it only works if I put the full path from the root of my machine, for example.
Any attempt to use a relative path, leads to the following error message.
This error message says the file is not found at the location that the file is in my project! As I mentioned above copying the full file path from the error into my scss file fixes the problem, but clearly that is not a solution.
I've tried adding postcss-import and adding '.' to the path, but that had no effect.
Not sure if this is a bug or config issue. So please excuse if I'm being dumb.
The text was updated successfully, but these errors were encountered: