# Problem with Bootstrap 4 and Font-Awesome 4.7 in Aurelia CLI (Webpack)

**URL:** <https://discourse.aurelia.io/t/problem-with-bootstrap-4-and-font-awesome-4-7-in-aurelia-cli-webpack/797>\
**Category:** Help Requests\
**Created:** [February 18, 2018, 11:32am UTC](https://discourse.aurelia.io/t/problem-with-bootstrap-4-and-font-awesome-4-7-in-aurelia-cli-webpack/797 "2018-02-18T11:32:50Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![shahabganji](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/shahabganji/32/1539_2.png) [@shahabganji](https://discourse.aurelia.io/u/shahabganji)\
**Post date:** [February 21, 2018, 12:31pm UTC](https://discourse.aurelia.io/t/problem-with-bootstrap-4-and-font-awesome-4-7-in-aurelia-cli-webpack/797/21 "2018-02-21T12:31:01Z")

</div>

Thanks @MaximBalaganskiy

Firstly, I have to say that by ready to use I did not mean the optimal configuration, I meant that the toolbelt can now be used with those default templates with some tiny changes. 😄

Secondly, Actually I did not know this fact at all 😮 😉 , and honestly, I thought that it is awesome to separate them.

> your app and vendor bundles will have different module types in them - native and commonjs, which will prevent reusability and bloat app bundle.

Lastly, today @HamedFathi and I were talking about changing the webpack config of [asp.net](http://asp.net) core, to the aforementioned repo + your PR, just to make all starter-kits the same and easy to understand. yet, we did not know it is not **optimal**.

many thanks that you mentioned it.

[Previous page](https://discourse.aurelia.io/t/problem-with-bootstrap-4-and-font-awesome-4-7-in-aurelia-cli-webpack/797.md?page=1)