Handle asset dependencies with bower
Installs: 398 349
Open Issues: 17
- php: >=5.3.3
- doctrine/cache: ~1.0
- doctrine/collections: 1.*
- symfony/assetic-bundle: ~2.1
- symfony/framework-bundle: ~2.1 | ~3.0
- symfony/process: ~2.3,>=2.3.20 | ~2.4,>=2.4.10 | ~2.5,>=2.5.5 | ~3.0
- phpunit/phpunit: 4.0.*
- symfony/console: ~2.1
The SpBowerBundle adds support for handling asset dependencies with bower in a nice way.
- Install bower packages in your bundles with one command
- Register all installed bower packages as assets so they can be used in templates
- Unit tested
Caution: This bundle is developed in sync with symfony's repository.
⚠️ This Project Has Been Deprecated ⚠️
Thank you for your interest in contributing to this bundle. Unfortunately, I do not plan to continue maintaining this bundle.
With symfony 3.0 assetic was removed (at least in the standard edition) and some time later the new Webpack Encore component was announced, thus (and the fact that I stopped using bower myself a while ago) I will no longer maintain this bundle.
Feel free to use this bundle as-is but I strongly recommend using other tools for asset management (like grunt, gulp or webpack). If you have a project depending on this bundle, I would recommend on migrating it to something else.
If someone wants to take over this bundle, let me know and I will gladly transfer the ownership.
Thanks for your support and using this bundle over the years.
Bower >= 1.0.0
Since version 0.8 the bundle fully supports bower
If you used version 0.7 before, you might want to read the upgrade instructions to 0.8.
Bower < 1.0.0
If you are still using a bower version
< 1.0.0, you must use a Version lower or equal to
0.7 from this bundle.
Read the Documentation for master
Read the Documentation for 0.1
All the installation instructions are located in the documentation.
This bundle is under the MIT license. See the complete license in the bundle:
Reporting an issue or a feature request
Issues and feature requests are tracked in the Github issue tracker.
When reporting a bug, it may be a good idea to reproduce it in a basic project built using the Symfony Standard Edition to allow developers of the bundle to reproduce the issue by simply cloning it and following some steps.