Many of you, like us, may continue to encounter numerous errors while using the app. One of the most frequently asked errors, for example, is “TypeError: angularCompiler.getResourceDependencies(…) is not a function or its return value is not iterable“. So, how can this be resolved? We will discuss together to figure out the best solutions for you.

When Does The Error “TypeError: angularCompiler.getResourceDependencies(…) is not a function or its return value is not iterable ” Happen?

When you ran the angular project on 10.0.1, it reported many low vulnerabilities and a few high ones. So you used the npm audit fix to correct them and get the following errors:

Error: ./src/main.ts  

Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):

TypeError: angularCompiler.getResourceDependencies(...) is not a function or its return value is not iterable

    at getDependencies (C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:261:56)

    at C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:374:20

    at analyzingFileEmitter (C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:307:20)

    at process._tickCallback (internal/process/next_tick.js:68:7)

Error: ./src/polyfills.ts  

Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):

TypeError: angularCompiler.getResourceDependencies(...) is not a function or its return value is not iterable

    at getDependencies (C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:261:56)

    at C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:374:20

    at analyzingFileEmitter (C:\Web\vgc\vgc\node_modules\@ngtools\webpack\src\ivy\plugin.js:307:20)

    at process._tickCallback (internal/process/next_tick.js:68:7)

Simple Solutions For ”TypeError: angularCompiler.getResourceDependencies(…) is not a function or its return value is not iterable” Error

Solution 1: Update to Angular 11

An open source JavaScript MVC framework for web applications is called Angular. It expands HTML and gives it dynamic functionality. It is maintained by Google, and its main use is to build single-page applications. Angular is a framework with undeniable benefits that also gives programmers a uniform framework to work with. It gives users the ability to make huge apps in a manageable way.

Updating to Angular 11. is a great way for you to resolve the error ”TypeError: angularCompiler.getResourceDependencies(…) is not a function or its return value is not iterable”. You need to update our Angular Version to the most recent version. This method will work for you.

@angular/core @angular/cli @angular/cli @angular/cli @angular/cli @angular/cli @angular/cli @angular/

Both commands will update Angular to the most recent version.

It is our work.

Solution 2: Use the code in this way

You may use the code in this way to resolve this error. TRY IT OUT. This solution may be suitable for you. This solution is also effective for us.

rm -rf node modules/

npm install 

npm run build 

Your error will disappear after you do it.

Solution 3: Use the following code

The last solution may work for you, and you can use the following code.

rmdir /s node_modules

npm install "or" npm install @angular-devkit/build-angular

npm run build

The solutions mentioned above are very simple, aren’t they? However, their efficiencies are very enormous. They work perfectly. After use them, your error will be completely resolved and there is not any error in your program. So, what are you waiting without applying them for your problem to get the desired results?

Conclusion

If you’re stuck on the error “TypeError: angularCompiler.getResourceDependencies(…) is not a function or its return value is not iterable“, the remedies listed above are the fastest way. People have a growing community where everybody is usually willing to help if you still need advice or have frequent questions. Finally, we hope you’re having fun with the amazing code options and appreciate spending time reading.

Read more

→ TypeError: ‘Series’ Objects Are Mutable, Thus They Cannot Be Hashed