Our team is currently working on implementing ahead of time (AOT) compilation for our Angular 2 project, but we have encountered an error:
Error: Internal state: StaticSymbols in summaries can't have members! {"filePath":"C:/Users/bhavy/Documents/projects/kairos/projects/KairosUI/node_modules/daypilot-pro-angular/daypilot-angular.min.d.ts","name":"DayPilot","members":["Angular","Scheduler"]}
Error: Internal state: StaticSymbols in summaries can't have members! {"filePath":"C:/Users/bhavy/Documents/projects/kairos/projects/KairosUI/node_modules/daypilot-pro-angular/daypilot-angular.min.d.ts","name":"DayPilot","members":["Angular","Scheduler"]} at AotSummaryResolver._assertNoMembers (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:26300:23) at AotSummaryResolver.resolveSummary (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:26308:18) at CompileMetadataResolver._loadSummary (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:18032:70) at CompileMetadataResolver.getNgModuleSummary (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:18226:56) at C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:18318:72 at Array.forEach (native) at CompileMetadataResolver.getNgModuleMetadata (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:18313:53) at addNgModule (C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:25053:62) at C:\Users\bhavy\Documents\projects\kairos\projects\kairosUI\node_modules\@angular\compiler\bundles\compiler.umd.js:25064:18 at Array.forEach (native) Compilation failed.
What is the significance of this error? Which specific static symbols are being referenced here?
It's crucial to understand the nature of the error before attempting to resolve it.
Any assistance or recommendations that you may have would be greatly appreciated.
PS: While we initially tried reporting the issue on the Angular GitHub page tracker, they suggested that Stack Overflow might be a more suitable platform to address these kinds of support issues.