You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's hard for me to tell what's failing in my Gemfile, but here's an overview.
Compass was working normally before I ran 'bundle update' today. I checked through all the gems that were updated in 'Gemfile.lock' and reverted them all back to the previous working versions. Then I disabled them one by one and narrowed it down to sassy-maps.
Phew.
When running 'bundle exec compass watch', using sassy-maps 0.4.0 on a Windows machine, I get this error:
WDM::Error on line ["73"] of C: Can't get the absolute path for the passed directory: ''!
Run with --trace to see the full backtrace
When I revert back to version to 0.3.2, Compass watch works normally.
It's hard for me to tell what's failing in my Gemfile, but here's an overview.
Compass was working normally before I ran 'bundle update' today. I checked through all the gems that were updated in 'Gemfile.lock' and reverted them all back to the previous working versions. Then I disabled them one by one and narrowed it down to sassy-maps.
Phew.
When running 'bundle exec compass watch', using sassy-maps 0.4.0 on a Windows machine, I get this error:
When I revert back to version to 0.3.2, Compass watch works normally.
Here's my Gemfile:
Using Ruby 2.0.0p353
The text was updated successfully, but these errors were encountered: