-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Add support for "to" postcss option #145
Comments
Ping! |
This issue is still actual even for newer version of this plugin. The fix is small, backward compatible and will improve support for other postcss plugins. Please let me know if you are ok with proposed approach and I will created PR with this change. Thank tou. |
Ping! |
Here is a PR for this change: #163 |
postcss-url is also affected by this issue. |
🎉 This issue has been resolved in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Current version if this plugin has hardcoded "to" value to be the same as "from". This breaks a lot of postcss plugins that are relying on source/target filenames to properly rebase asset urls.
Example of affected plugin: https://github.com/sebastian-software/postcss-smart-asset
Technically, any rebase plugin that is relying on
from
orto
won't work as expected with currently hardcodedfrom
andto
.Would you be open to accept a small PR fix that will do this (so "to" could be explicitly passed when it is needed):
The text was updated successfully, but these errors were encountered: