I’m experiencing longer build times after integrating the Sisense Angular SDK into my project. Profiling suggests that CommonJS/AMD dependencies in the SDK are triggering optimization bailouts during the build process.Has anyone encountered similar issues with the Sisense SDK? I’m looking for strategies to reduce these bailouts or optimize the integration to better fit Angular’s ES module requirements. Any advice on how to improve build performance while using this SDK would be greatly appreciat...

herajapakse and IsaacBlanco yesterday we released CSDK 1.18.0 that contains a fix for this. Please give it a try and let us know if it resolves your issue.

Mitigating Optimization Bailouts in Angular with Sisense SDK: Handling CommonJS/AMD Dependencies | Help and How-To

MoreDiscussions

Mitigating Optimization Bailouts in Angular with Sisense SDK: Handling CommonJS/AMD Dependencies | Help and How-To | Sisense Community