-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
Issue with sass and postcss/autoprefixer #74
Comments
Could you show full error stacktrace? |
The stacktrace is too long to post here as it contains the full sass processed bootstrap code. Here is the another version with the beginning :
|
I am running into a similar issue; I spent some time trying to create a reduced test case but didn't have any luck. I think this is due to some bad combination of webpack, Babel, postcss, postcss-loader, and maybe some other things that I haven't tracked down yet. Right now I'm only able to repro this when npm link-ing to a local version of a dependency; loading the same (private) dependency from a git URL works fine. I will do my best to get you more details as I find them, but in the meantime I wanted to share a fuller stack trace in case it's helpful.
|
OK; I feel like I've eliminated any potential dependency conflicts, and what I'm seeing now is this:
I'm sharing this not because it makes any sense to me, but in the hopes maybe it will trigger a light bulb for someone else. |
I think for me what was happening was webpack was looking for the postcss-loader module but, due to how webpack does loader resolution, it was finding the regular postcss module and trying to use it instead. When I installed the postcss-loader module in Module2, the problem went away. Given that Module2 doesn't itself need postcss-loader, this is a bummer, but doesn't really have anything to do with postcss-loader itself. This seems to be an issue with how webpack does loader resolution when it comes to linked modules. I think none of this was happening in the "normal" installation case because webpack was properly finding the postcss-loader module. I'm using NPM3; I can imagine that if a project was using NPM2, it could possibly run into this situation even in the normal installation case, but I'm not sure. |
Just for others who came here with this problem from google like I did. It's exactly as @rmurphey says, although I had a much simpler problem: I had To fix: |
@tackley I love you |
@tackley me too! |
@tackley papa bless |
@tackley thanks for saving my life |
@tackley hahha thanks for save my life |
Thanks @tackley |
@tackley Love you too! |
Thanks @tackley && @michael-ciniawsky Saved me a whole day of googling! |
Here is my webpack config file :
The text was updated successfully, but these errors were encountered: