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 have a rails application with huge amounts of assets due to some frontend frameworks. In config/initializers/assets.rb I use wildcard selectors to precompile all assets for production.
When starting the rails sever for development, the first request takes forever, presumably because all assets are being precompiled. This seems to happen only with the newer versions of sprockets-rails (3.1).
Older versions of sprockets-rails (2.3.3) would load just fine. My feeling is that older versions would not compile all the assets greedily, but only when needed, while never versions seem to compile them all upfront.
I have a rails application with huge amounts of assets due to some frontend frameworks. In
config/initializers/assets.rb
I use wildcard selectors to precompile all assets for production.When starting the rails sever for development, the first request takes forever, presumably because all assets are being precompiled. This seems to happen only with the newer versions of sprockets-rails (3.1).
Older versions of sprockets-rails (2.3.3) would load just fine. My feeling is that older versions would not compile all the assets greedily, but only when needed, while never versions seem to compile them all upfront.
Is this behaviour intended?
I made a small example app to demonstrate the issue.
The text was updated successfully, but these errors were encountered: