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
Testing my change installing "postcss-url": "thisconnect/postcss-url#Fix-assetsPath" all it does is not include the dirname stuff when creating the relativeAssetsPath. Works fine for me, unfortunately I believe there is no test coverage at all for this.
Yep, after applying it manually it somehow works better, but unfortunately I still get wrong paths in my monorepo project. Anyway, it seems to be a completely different story.
Btw. I've added it manually but in a long term I have to add it somewhere as a local code in my repo or even better as a npm package. Do you guys have some speed method of adding it as a fork so that I can install my fixed version?
Or maybe, there is someone who could check all pull requests and merge them?
Hi guys, just ran into this issue today and I'd like to know if anybody figured the best option here...
It seems that useHash: true is kinda mandatory for postcss-url to work. Also, I'm amazed this hasn't gotten any attention so far, is there a solution besides waiting for #146 to be merged? Has someone managed to get the core team's attention on the matter?
Activity
thisconnect commentedon Jan 7, 2016
I can confirm that there is something wrong with
useHash: false.src/styles.css
config/styles.js
With
useHash: falseI end up with a weird unexpected file structureWith
useHash: trueall is good and the fonts are copied intodist/styles/fonts/thisconnect commentedon Jan 7, 2016
happens here https://github.com/postcss/postcss-url/blob/master/index.js#L298...L303
Trying to figure out what this regex is supposed to do, I'm not good at understanding others Regex :(
thisconnect commentedon Jan 7, 2016
Got introduced here 59683e5
thisconnect commentedon Jan 7, 2016
Testing my change installing
"postcss-url": "thisconnect/postcss-url#Fix-assetsPath"all it does is not include the dirname stuff when creating the relativeAssetsPath. Works fine for me, unfortunately I believe there is no test coverage at all for this.hugmanrique commentedon Jun 2, 2018
Any updates on this?
MadadiSaeed commentedon Aug 29, 2020
I can confirm too. version 8.0.0
rproserpio commentedon Oct 22, 2020
Probably fixed by #146
Nagell commentedon Jan 7, 2022
nope, it's still a bug
rproserpio commentedon Jan 7, 2022
That PR hasn't been merged. It's still a bug after manually applying the patch?
Nagell commentedon Jan 10, 2022
Yep, after applying it manually it somehow works better, but unfortunately I still get wrong paths in my monorepo project. Anyway, it seems to be a completely different story.
Nagell commentedon Jan 11, 2022
Btw. I've added it manually but in a long term I have to add it somewhere as a local code in my repo or even better as a npm package. Do you guys have some speed method of adding it as a fork so that I can install my fixed version?
Or maybe, there is someone who could check all pull requests and merge them?
rproserpio commentedon Jan 11, 2022
I do sometimes use https://github.com/ds300/patch-package
Nagell commentedon Jan 11, 2022
Oh man! That's a damn good tip. I owe you a beer :)
thiagomajesk commentedon Jan 16, 2022
Hi guys, just ran into this issue today and I'd like to know if anybody figured the best option here...
It seems that
useHash: trueis kinda mandatory forpostcss-urlto work. Also, I'm amazed this hasn't gotten any attention so far, is there a solution besides waiting for #146 to be merged? Has someone managed to get the core team's attention on the matter?msteller-connyun commentedon Jan 31, 2024
Just had also this bug. It's a big ridiculous that this is still not fixed - after 8 years. And a PR with a fix exists.
Is postcss-url abandoned?