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

@jeremyholt, @MaximBalaganskiy, @veccsolutions

I just want to clarify sth, we are NOT using fusebox to write the toolbelt, we are using fusebox to bundle the modules for the sample and docs you see on the demo page. That, and the fact that at the time we started writing the toolbelt we did not know the knots and bolts of major bundlers, we preferred to work with one which has fewer problems than others and is more straightforward, and the skeleton provided by @vegarringdal paved the way.

Moreover, even now, that we know how to configure the basics of webpack or AureliaCLI/requireJS we confront serious obstacles, they are for sure due to lack of my understanding or knowledge around those bundlers:

  1. With webpack configuration provided in aspnet core spa templates the jquery was undefined when we are using some specific components such as bootstrap-toggle2 or tokenize, removing them all is good, weird to me :smile: thus, I added jquery as a static-or-CDN-base resource in my index.html, and all problems solved. check here and here and here.

  2. Using webpack configuration provided by CLI we even face more problems, that @MaximBalaganskiy and @HamedFathi worked on that for a day I guess, am not sure at the moment whether they succeed or not, when I replaced the configuration of CSS loaders with the one provided in spa templates we face no error but the CSS does not get into the bundles. Do I need to add all of them as static CSS resources too? :weary: :smile:

  3. The same story happens when using AU/CLI and requireJS, there are a lot of javascript files that the bundler just ignores them, and I have no idea why that happens, take a look at here.

  4. In requireJS, we have to import CSS files like this

import 'text!some_path_to_css_files/file.css';

for webpack:

import 'some_path_to_css_files/file.css';

put aside that @noView() and @viewResources do not load nprogress CSS files into the bundle and I have to use the import syntax. When using webpack.

Still, I have some more complicated issues, I don’t know how to explain.

Our main concern is only around providing a basic configuration for the Aurelia community to use the toolbelt as easy as possible. Like what @zewa666 requested and what we have done for webpack config.

To conclude, having starter kits can help people to better config their developing environment, that’s why we are trying to create some here.

I think asp.net core starter kit is ready to work with.

Regards,
Shahab