Error: Cannot resolve type entity i1.FontAwesomeModule to symbol
See original GitHub issueDescribe the problem
when I run ng build
I get this error
Error: Module build failed (from ../../node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Cannot resolve type entity i1.FontAwesomeModule to symbol
at node_modules\@ngtools\webpack\src\ivy\loader.js:81:18
at processTicksAndRejections (node:internal/process/task_queues:96:5)
What did you expect?
to build without errors
Reproducible test case
repo
run cd ngx-cms && npm run tmp
Issue Analytics
- State:
- Created a year ago
- Comments:9
Top Results From Across the Web
Error: Cannot resolve type entity i10.BidiModule to symbol ...
I ran into this very same issue today. I had a library project for Angular 13 and after adding the @angular/flex-layout as a...
Read more >Error: Cannot resolve type entity i3.DialogModule to symbol
In this post, you will learn how to fix Error: Cannot resolve type entity i3.DialogModule to symbol while updating Angular to version 14....
Read more >@fortawesome/angular-fontawesome - npm
Start using @fortawesome/angular-fontawesome in your project by running `npm i @fortawesome/angular-fontawesome`.
Read more >Cannot find module '@angular/core' or its corresponding type ...
i recently updated my project angular version from v11 to v14 the other version worked, but this. ... Error: Cannot resolve type entity...
Read more >Facing compile error during ng serve while setup of new ...
My versions are: Angular CLI: 14.2.7 Node: 14.20.1 Package Manager: npm ... Error: Cannot resolve type entity i5.BsDropdownModule to symbol.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@devoto13 Good news is I was able to trigger breakpoint in exception. Thank you very much for this launch configuration thing. Bad news is that I was unable to find that erroneous entity type: in the exception block the context is lost and the place where it happens is emitting
polyfills.ts
(this is whatresourcePath
tells me)… Does not help much, alas… Well, don’t want to bother you further with that. UPDATE: I am close to finding the root cause: I just needed to put the breakpoint inchunk-[BLABLA].js
file, which creates an interpolation of the error message and then analyzing the call stack.You’ll need to attach the debugger to the Node process building the application, not to the application running in the browser. If you use VS Code, then something like the below in the
.vscode/launch.json
should work:Add this configuration, open the
node_modules@ngtools\webpack\src\ivy\loader.js
file in the VS Code, put a breakpoint, run theng serve
configuration inside VS Code.