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
{{ message }}
Repository navigation
We should provide existing absolute paths for the source files #27
Recently, I had few problems with resolving paths in the postcss-url plugin.
I did a small research and found out that we provide non-existing absolute paths to the process() method.
I made two PRs which fix the problem: #25, css-modules/postcss-modules-scope#15
Unfortunately, those are breaking changes and we should publish them with new major version.
changed the title [-]We should use real absolute paths as the source files[/-][+]We should use real absolute paths for the source files[/+]on Sep 9, 2015
changed the title [-]We should use real absolute paths for the source files[/-][+]We should provide existing absolute paths for the source files[/+]on Sep 10, 2015
Activity
mightyaleksey commentedon Sep 9, 2015
Ah, and we need opportunity to pass the
tooption to thepostcss.process()method: https://github.com/postcss/postcss/blob/master/docs/api.md#processorprocesscss-opts[-]We should use real absolute paths as the source files[/-][+]We should use real absolute paths for the source files[/+][-]We should use real absolute paths for the source files[/-][+]We should provide existing absolute paths for the source files[/+]tinchoz49 commentedon Nov 5, 2015
👍 I have the same problem of @sullenor ! using postcss-copy.