I'm submitting a ... (check one with "x")
[x ] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
I am using this configuration with PrimeNG 5.2.0
Angular CLI: 1.7.1
Node: 6.11.2
OS: darwin x64
Angular: 5.2.6
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router
@angular/cli: 1.7.1
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.4.2
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.10.1
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.6.2
webpack: 3.11.0
I have added the css files to my angular-cli.json file:
"styles": [
"../node_modules/prismjs/themes/prism.css",
"../node_modules/@ngx-loading-bar/core/loading-bar.css",
"../node_modules/ng2-toastr/bundles/ng2-toastr.min.css",
"../node_modules/primeng/resources/themes/bootstrap/theme.css",
"../node_modules/primeng/resources/primeng.min.css",
"sass/designsystem/designsystem.scss",
"styles.scss"
],
All the other CSS files in this array are loading and working. PrimeNG itself works. However, there is none of your css applied.
I realize now that Font Awesome is a true requirement for any of your CSS to load. I wouldn't have expected that; I thought omitting it would just lose icons.
Most helpful comment
I realize now that Font Awesome is a true requirement for any of your CSS to load. I wouldn't have expected that; I thought omitting it would just lose icons.