Asier Garcia Calvo
Asier Garcia Calvo
Yes. This appears after changing index.ts to remove: module.exports = jsGantt.JSGantt; Because Angular fails if you mix module.exports & export. The other side efect in ng-gantt.ts I think is better...
It's weird, and It's mandatory to avoid this silly breaking change, I think. But I can't get it rigth. May can we ask for help opening an issue on this...
This library doesn't seems to work on Angular 16 due to this breaking change: `The Angular Compatibility Compiler (ngcc) was a build tool that facilitated compatibility between Angular's previous compiler...
I am using https://github.com/coreybutler/nvm-windows to switch node versions, it works for me with node v12.
Hi. Im my case this works (v.3.0.0) with node v12.22.12 but not with v18.16.1. The behavior is as #173
> Why this is not yet merged in? It is really helpful feature. +1 Migrating from Angular 8 to Angular 10.
> I'll definitely accept any well written PR to support ES modules. I'm pretty busy so I won't have time to work on this for a while myself. How about...