-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
postcss-loader changes the relative path of url()
function returned from sass-loader
#500
Comments
postcss-loader doesn't touch your url, double check your plugins |
Every time when we ask to create reproducible test repo, developers ignore us, but if you look at closed PR by me, you can found around 99% issues resolved by developers when they try to create reproducible test repo, they found problems in own environments and fix it |
Thank you a lot, I used 3rd party tools which hide most of the webpack configs. I only checked the |
Yes, only |
Yes, but what I am confused about is there was no I'm not familiar with webpack like you. Have you ever encountered this? Are there any plugins that touched this? I also fired an issue in the repo of that tool. But if you know that much appreciated. |
No
Yes, for example https://github.com/postcss/postcss-url |
I found that they created an additional plugin to touch this... |
Expected Behavior
I don't want
postcss-loader
to change the relative path inurl()
, so it can be resolved by the nextcss-loader
. Is there an option I can use to disable it?Actual Behavior
The path changed from
../assets/foo.png
to./foo.[hash:20].png
. And the file generated in the root of thedist
folder.Code
The text was updated successfully, but these errors were encountered: