"Maximum call stack size exceeded" in Angular 9 ng build --prod for a library

Question

I have a library that I'm able to compile with Angular 9. But if I change the flag to --prod, which practically makes "enableIvy": false then I get

[error] RangeError: Maximum call stack size exceeded

at Object.pathIsRelative (... ode_modules ypescript\lib ypescript.js:5778:34)

at tryLoadModuleUsingPathsIfEligible (... ode_modules ypescript\lib ypescript.js:28346:37)

at tryLoadModuleUsingOptionalResolutionSettings (... ode_modules ypescript\lib ypescript.js:28334:24)

at tryResolve (... ode_modules ypescript\lib ypescript.js:28479:28)

at ... ode_modules ypescript\lib ypescript.js:28471:69

at Object.forEach (... ode_modules ypescript\lib ypescript.js:309:30)

at nodeModuleNameResolverWorker (... ode_modules ypescript\lib ypescript.js:28471:25)

at nodeModuleNameResolver (... ode_modules ypescript\lib ypescript.js:28464:16)

at Object.resolveModuleName (... ode_modules ypescript\lib ypescript.js:28238:30)

at CompilerHostAdapter.getMetadataFor (... ode_modules@angular\compiler-cli\src\metadata\bundler.js:567:37)

I introduced a console debug message in function tryLoadModuleUsingPathsIfEligible(extensions, moduleName, loader, state) function and it seems to be a loop with approximately 20 moduleNames. I have to mention that I do NOT have any circular dependency warning if I compile without --prod flag.

Update: I fixed the circular dependencies and I have no more warnings of sort.

user_3639375 · Answer

I had the same problem with angular 12.1.1, I had no circular dependenicies, the solutution was to change "enableIvy: false" to "compilationMode": "partial".

See angular docs.

user_13440669 · Answer

Try deleting unnecessary imports, if anything like this:

'A' module imports 'B' module and vice versa

user_1713747 · Answer

In the end, aber rm -rf node_modules I also needed to do npm cache clean --force - also I made sure I really had all dependencies updated. (Not sure which of those things did the trick)

user_525886 · Answer

Been facing the same issue, in my case there was index.ts with invalid export

export * from './'

Fixed it and it build again with ng build

user_17291971 · Answer

First, remove node_modules and reinstall dependencies - this is a just in case solution. Generally, what happens is

Self Import in a module
Cycle dependency, cycle imports
recursive call with no termination

Be very careful to the 2 points in the beginning, as angular generally not showing that something is wrong in the imports. That may be a good reason for call stack size explosion. Hope it helps.

"Maximum call stack size exceeded" in Angular 9 ng build --prod for a library

5 Answers