13 Jul 2018, 18:30
I did not find a fix and unfortunately, I don't expect to. As a result, I simply stopped using PrimeNG. Before Angular Material, PrimeNG made a lot of sense for my projects. But their components are cumbersome & poorly (un)supported and the documentation is pretty horrible. I don't mean to insult the PrimeNG solution - I think it has a lot of potential and I have definitely found it to be useful at times. And perhaps the paid version is better?? But the documentation is almost always unnecessarily over-complicated, while still somehow failing to fully document proper usage. I have often found the documentation to be very out-dated - not matching current releases of the package, or even of Angular itself. In fact, as of very recently (at least up until June of 2018), it STILL referenced "angular2" imports instead of "@angular" in some places - which is crazy considering how long ago Angular transitioned to the "@angular" namespace.
Overall, I like PrimeNG and I have recommended it to colleagues. But they need to step up their game with testing & documentation. They obviously have a good design team and they are pretty well dialed in to the inner workings of Angular. For the product to come this far and fall short in this way is a real shame.
For this issue, the export functionality wasn't critical for my project. I only included it because it previously worked on an earlier version. So removing it wasn't a problem for me and the users didn't care. And with the tremendous progress that Angular Material has made in the past year or so, I see little reason to add a layer of complexity if it doesn't need to be there.