This Laravel 4 package provides a very simple and easy to use asset pipeline. It was heavily inspired by the Rails asset pipeline. We make use of the wonderful Assetic package to help with pre-compliation!
There's no reason to use facades in a service provider (as is done by including routes.php).
I'd suggest just moving the code in routes.php to the service provider - as it's just three lines - and then accessing the router and config through the app object, like so:
There's no reason to use facades in a service provider (as is done by including routes.php).
I'd suggest just moving the code in routes.php to the service provider - as it's just three lines - and then accessing the router and config through the app object, like so: