angular-fontawesome | Official Angular component for Font Awesome | Awesome List library

In my Angular project I try to use Google Chrome for testing with Karma & Jasmine in a GitHub Action.

The Google Chrome start with multiple errors, and then dies after some tests. I tried several tips from StackOverflow ansers in this topic, but nothing helped.

I use this versions:

• Chrome 99.0.4844.51 (latest at this time)
• Karma 6.3.16
• Angular 13.2.3 (I think it's not relevant, but I don't know)

I have this karma.conf.js file:

When using fontawesome with the link to the css from cdn it is possible to use css to put icons e.g. inside buttons like this:

I have created an FAIcon Module and i am using FaiconLibrary.addIcons() method to include few icons. This was working perfectly fine but just now, i got fresh copy and did npm install and started getting following error. I tried removing node_modules and did clean cache as well, did't work.

Im using angular-fontawesome and want to change the background color of an font-awesome fa-icon

I have upgraded my angular to angular 13. when I run to build SSR it gives me following error.

I have a pipeline that does an npm install followed by angular build and recently I added a caching task to relieve installation which was working splendidly until the developer added a new private dependency of "runtime-config-loader": "^3.0.0".

This may require npm re-install again, however, for some reason the caching task doesn't think it requires a re-install, and so it skips over the npm install and then fails at the angular build, most likely because npm did not re-install on the agent.

I disabled the caching task and removed the custom condition eq(variables['CACHE_RESTORED'],False) from the npm install task, and the build is succeeding just fine.

Why is the cache not recognizing the need to re-install dependencies again? and how do I delete the cache so that npm installs again? As a reminder, when I disable the cache task and npm re-installs again on the agent, the build succeeds - so this is certainly a caching problem.

Here is the build YAML:

I am having problem with angular 12 sub routes. I can navigate to the sub routes just fine but when I refresh the page I lose context. I am running it locally on the localhost:4200 here is the image of what I am getting in network tab and on the screen when I refresh enter image description here

here is a link for source code: https://github.com/Stanmozolevskiy/Portfolio

Here is routing component:

When we are trying to update our Angular 9 application(Single SPA micro frontend) to Angular 12 we are facing bellow issue.

Error on console when trying to run this app:

I have installed windows 11 in my newly bought laptop, and installed Nodejs, Angular Cli, but when I run npm install in my project everything is giving error, I tried a lot , but could not solve it.

upgrade downgrade node. update all node packages. clear cache etc.

Note: