Relative imports don't work if no from option given

[lboecker]

Let's assume the following project structure:

• ./gulpfile.js
• ./css/main.css
• ./css/lists.css

main.css contains the following line: @import "lists.css";

This currently doesn't work without passing { path: ['css'] } to postcss-import. This is probably related to #7, but I feel like relative imports should just work despite of what postcss-import does after it decided that it's not a relative import (e.g., look for node_modules/lists.css/ or something like that).

[MoOx]

If you look at fixtures, relative import are supposed to work (if you have provide the from option into postcss).
I use postcss-import without any path option & relative import work for me. That being said, I'll take a second look asap since tests use a path.
And the readme should mention the fact that from option helps to make relative import works.
Can you tell me if you use from option or not ?

[lboecker]

@MoOx My bad, I didn't know the from option even existed. I use the path array and it seems to be doing pretty much the same thing.

Looks like the import plugin prepends the from path to it's path array. I think it's a good idea to just prepend the current stylesheet's parent directory as well.

[MoOx]

We don't have the current stylesheet information since postcss process css string. That's why we use from option.

[lboecker]

Makes sense. You may want to explicitly point this out in the readme so that folks like me don't bug you with issues all day. :P Keep up the good work.

[MoOx]

I'll let that issue open to remind me that ;)