3 ms·
Thanks for more details -- is this documented anywhere yet? If not, it might be good to add to the "docs needed" checklist. (Also, if when migrating an app fro
by jrochkind1 14y ago
Thanks for more details -- is this documented anywhere yet? If not, it might be good to add to the "docs needed" checklist.
(Also, if when migrating an app from 3 to 4 you need to manually add 'sprockets-rails' to your Gemfile, should be mentioned in migration guide)
It seems unfortunate to me that all those gems involved only in asset compiling now need to be in every environment -- meaning they need to actually be loaded and 'require'd in your production running app, even though assets have already been compiled. Hopefully that change to requirements was needed to reap some worthwhile benefit, it's still pretty sketchy to me why the sprockets integration improvements led to this change.
- steveklabnik 14y agoI am not 100% sure. I'll talk to the people in charge of the asset pipeline and get it in there. > it's still pretty sketchy to me why the sprockets integration improvements led to this change. Sprockets is one of the parts of Rails I know least about, so yeah, I'm not sure why this decision was made. But explaining it somewhere for posterity is a good thing, absolutely.