Closed bb closed 1 year ago
i just ran into this same error, on ruby 3.2.2 / rails 7.1.0.alpha with sprockets but no pre-processing of css/js assets (so no sass).
Bit me too. Using Rails 7 with esbuild/tailwindcss (so no need for SASS in this project at all)
Looking at https://github.com/BetterErrors/better_errors/pull/498/files it looks like the original plan was indeed to bundle the compiled css:
When the gem is built (in CI), main.css is built with the compressed CSS and included in the gem. The scss files are not included in the gem.
So the ErrorPageStyle
module should probably just be split into the runtime part (which doesn't depend on scss) and the development part which does.
Can you please clarify whether it is necessary for projects using better_errors
to also include sassc
as a development dependency explicitly or will there be a new version that resolves this?
Hi , any update on this ?
Looks like this issue can be closed. It has been fixed by #520 in better_errors 2.10.1.
Thank you @RobinDaugherty and @jackjennings!
I just tried to upgrade from 2.9.1 to 2.10.0 in a Rails project which is not using sassc itself.
The new version depends on sassc and is using it in
better_errors-2.10.0/lib/better_errors/error_page_style.rb:1
without actually depending on it in the Gemfile.This results in an Error when trying to run console or server:
Alternatively (and for me preferably), maybe the sass files could be compiled into the published Gem?