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
I was just trying to update a rails application with bundle update and ran into a problem (using Ubuntu 18.04 with ruby 2.5.1p57.
The rails app includes sass style sheets (I do prefer sass over scss), which was working when using the app for the last time. Nowadays the gem sass-rails is outdated and deprecated, therefore I uses sassc-rails.
After upgrading I could not precompile the assets anymore:
% rake assets:precompile
rake aborted!
Sprockets::FileNotFound: couldn't find file 'applicationtest.sass' with type 'text/css'
Checked in these paths:
...
After tracking this down step by step, I found that just a single difference in Gemfile.lock causes the problem:
sprockets (3.7.2) works and compiles the sass
sprockets (4.0.2) does not work, issues that error message.
The text was updated successfully, but these errors were encountered:
Hello! Thanks for opening up an issue. In order to move forwards with this issue I'll need an example app that reproduces the behavior (https://www.codetriage.com/example_app).
Hi,
I was just trying to update a rails application with bundle update and ran into a problem (using Ubuntu 18.04 with ruby 2.5.1p57.
The rails app includes sass style sheets (I do prefer sass over scss), which was working when using the app for the last time. Nowadays the gem sass-rails is outdated and deprecated, therefore I uses sassc-rails.
After upgrading I could not precompile the assets anymore:
% rake assets:precompile
rake aborted!
Sprockets::FileNotFound: couldn't find file 'applicationtest.sass' with type 'text/css'
Checked in these paths:
...
After tracking this down step by step, I found that just a single difference in Gemfile.lock causes the problem:
sprockets (3.7.2) works and compiles the sass
sprockets (4.0.2) does not work, issues that error message.
The text was updated successfully, but these errors were encountered: