sp/bower-bundle

Handle asset dependencies with bower

SpBowerBundle

The SpBowerBundle adds support for handling asset dependencies with bower in a nice way., _(*1)

Features included:, _(*2)

• 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., _(*3)

:warning: This Project Has Been Deprecated :warning:

Thank you for your interest in contributing to this bundle. Unfortunately, I do not plan to continue maintaining this bundle., _(*4)

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., _(*5)

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., _(*6)

If someone wants to take over this bundle, let me know and I will gladly transfer the ownership., _(*7)

Thanks for your support and using this bundle over the years., _(*8)

Bower >= 1.0.0

Since version 0.8 the bundle fully supports bower >= 1.0.0. If you used version 0.7 before, you might want to read the upgrade instructions to 0.8., _(*9)

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., _(*10)

, _(*11)

Documentation

Read the Documentation for master, _(*12)

Read the Documentation for 0.1, _(*13)

Installation

All the installation instructions are located in the documentation., _(*14)

License

This bundle is under the MIT license. See the complete license in the bundle:, _(*15)

Resources/meta/LICENSE

Reporting an issue or a feature request

Issues and feature requests are tracked in the Github issue tracker., _(*16)

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., _(*17)