ERROR in Failed to compile entry-point angular-font-awesome (es2015 as esm2015) due to compilation errors

While executing the ng serve command I am getting the error below after updating angular version 8 to 9:

0% compiling
Compiling angular-font-awesome : es2015 as esm2015

chunk {main} main.js, main.js.map (main) 2.07 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 677 bytes [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered]
chunk {scripts} scripts.js, scripts.js.map (scripts) 168 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 2.25 MB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 342 kB [initial] [rendered]
Date: 2020-08-20T18:45:45.144Z - Hash: accfc9d111ebf6532cd5 - Time: 4333ms

ERROR in Failed to compile entry-point angular-font-awesome (es2015 as esm2015) due to compilation errors:
node_modules/angular-font-awesome/dist/angular-font-awesome.js:3968:26 - error NG1010: Value at position 0 in the NgModule.imports of AngularFontAwesomeModule is not a reference: [object Object]
3968                 imports: [CommonModule],
                            

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **

Can anyone help me out to solve this problem?

EDIT: The actual root cause of this issue is that there’s a type-only import in @ngxs/store/operators into @ngxs/store, which is only present in the .d.ts files. Because of this, ngcc does not determine @ngxs/store as a dependency, as it determines dependencies from the source files, not the typing files. Consequently, @ngxs/store/operators is processed before @ngxs/store is processed, and more importantly is it processed before the transitive dep on @angular/core is processed, while still consuming the .d.ts files of @angular/core because it’s a transitive dep. As such, the file system cache has been primed with .d.ts files of @angular/core before it has been processed, so updates to these declarations in another worker will not be taken into account as the stale cache entry is not evicted.

Hope this helps.

Regards,
Bruce