Skip to content
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

We should provide existing absolute paths for the source files #27

Open
mightyaleksey opened this issue Sep 9, 2015 · 2 comments
Open

Comments

@mightyaleksey
Copy link
Member

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.

Also I haven't checked css-modulesify yet.

@mightyaleksey
Copy link
Member Author

Ah, and we need opportunity to pass the to option to the postcss.process() method: https://github.com/postcss/postcss/blob/master/docs/api.md#processorprocesscss-opts

@mightyaleksey mightyaleksey changed the title We should use real absolute paths as the source files We should use real absolute paths for the source files Sep 9, 2015
@mightyaleksey mightyaleksey changed the title We should use real absolute paths for the source files We should provide existing absolute paths for the source files Sep 10, 2015
@tinchoz49
Copy link

👍 I have the same problem of @sullenor ! using postcss-copy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants