> Merge all those together, serving up 80 separate assets is insane. Isn't it?
That's what happens by default when using the asset pipeline when in the "development" environment, it's supposed to ease debugging and works well when only including a few JS files. In "production" all the files would be merged into 1.
There is a flag "config.assets.debug = true" in the "development.rb" file, switching that to "false" will output just one file.
Which, sadly, we've had to do in development as something has been introduced into Rails or sprockets that makes our development environment so slow it's unbearable with asset debugging enabled.
It really hurts not having the ability to dive into the separate files.
Comments
> Merge all those together, serving up 80 separate assets is insane. Isn't it?
That's what happens by default when using the asset pipeline when in the "development" environment, it's supposed to ease debugging and works well when only including a few JS files. In "production" all the files would be merged into 1.
There is a flag "config.assets.debug = true" in the "development.rb" file, switching that to "false" will output just one file.
Which, sadly, we've had to do in development as something has been introduced into Rails or sprockets that makes our development environment so slow it's unbearable with asset debugging enabled.
It really hurts not having the ability to dive into the separate files.