Rafael Mendonça França
Rafael Mendonça França
Is `node_modules` is your assets paths?
Can you provide an example application that reproduce the issue?
For sprockets 4 people should use the manifest file. We already raise an error when you boot the app and has no manifest file. We probably just need to expand...
_From @stepheneb on April 3, 2017 20:17_ Example repo with simple Rails 5.1.rc1 app. At this commit referencing the sass var from `application.scss` works: https://github.com/stepheneb/sass-demo/commit/bf854ab3a02d99235db665094c3cc32d692a4140 At next commit referencing sass...
_From @RemyMaucourt on April 21, 2017 13:29_ I have the exact same problem with sass-rails 6.0.0.beta1.
I don't remember in any change in the Rails framework or sass-rails that could cause this. What is the behavior in sass command line?
Just confirmed that the sass behavior is what you are expecting.
I tried to find when this changed and I could not find a combination of version where this used to work. Do you know if it ever worked?
_From @stepheneb on April 21, 2017 16:47_ @rafaelfranca can you describe more how you tested for the correct behavior? I tested with new Rails 5.1.rc1 app in this simple repo...
I tried both Rails 5.0.2 and 5.1. With both sass-rails 5.0.x and 6.x and sprockets 3 an I could not get that working. If you could make the sass-demo repo...