File-based modularised definitions not propagating up. about postcss-custom-media HOT 9 CLOSED

@Panoplos I was able to get my app working with https://github.com/MoOx/postcss-cssnext instead. It includes its own support for custom media queries (along with a lot of other great features).

from postcss-custom-media.

OK, it looks like the @import (reference) is the issue. If I remove that, it works, but this is because this copies all the contents of the imported files into the local file, which is undesired and is the whole reason to use reference. For instance, I am using semantic-ui, which is large enough on its own, let alone if it gets imported into every file. The workaround is to include settings.less directly without the (reference), but I would like to get this module working with reference imports. Is there a way to do this?

from postcss-custom-media.

@Panoplos Did you ever figure something out for this?

from postcss-custom-media.

No, this seems like a bug. I guess this project is dead?

from postcss-custom-media.

Your issue seems to related to a combination of things. It's fair that this project would not be responsible for import statements, and that seems to be at least part of this issue. Which tool are you using to accomplish that? Is it another PostCSS plugin? Are you able to create a reduced test case with only the bare minimum tools required to break this?

from postcss-custom-media.

You can see the tool chain in the error, and I think the information above is clearly enough to reproduce easily.

from postcss-custom-media.

I may have to abandon this plugin for that one...

from postcss-custom-media.

I'm using postcss-cssnext and experiencing the same issue. Is there any progress on this?

from postcss-custom-media.

This plugin has been rewritten. If any problems persist, please create a new issue.

from postcss-custom-media.