# \[Plugin\] Conflict when using angular bootstrap

**URL:** <https://discuss.elastic.co/t/plugin-conflict-when-using-angular-bootstrap/74507>\
**Category:** Kibana\
**Created:** [February 9, 2017, 1:26pm UTC](https://discuss.elastic.co/t/plugin-conflict-when-using-angular-bootstrap/74507 "2017-02-09T13:26:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\
**Post date:** [February 9, 2017, 7:05pm UTC](https://discuss.elastic.co/t/plugin-conflict-when-using-angular-bootstrap/74507/2 "2017-02-09T19:05:23Z")

</div>

Hi Alin,

If your plugin has dependencies which conflict with those in Kibana, it sounds like you have three options:

1. Fork Kibana and update the dependencies (not recommended because this will be very difficult for you to maintain as we develop Kibana).
2. Create a PR into Kibana which updates angular-ui-bootstrap to the version you need (may be somewhat difficult, but not impossible).
3. Use a different dependency or fork the dependency and downgrade the version of angular-ui-bootstrap it uses (not sure how hard this will be; I think you're in a better position to determine this).

I'd recommend trying #2 first. I'd be happy to review your PR and help you get it merged in, just tag me @cjcenizal when you submit it. If that doesn't work, I'd suggest #3. Sometimes taking control over a dependency is best because you can decide exactly what code makes it into your codebase. #1 is the nuclear option and not recommended.

Hope this helps!

Thanks,  
CJ

---

_[View the full topic](https://discuss.elastic.co/t/plugin-conflict-when-using-angular-bootstrap/74507)._