asked on October 21, 2019
Hello,
I have created a fresh Angular App (v 8.2.11 with "ng new") and just simple added ngFlexMonster.
In the production build, while generating differential loading for es5, it gets stuck. However, it runs well in Angular v 8.1.3 as per this repo.
It would be really helpful for me if you could take a look at this issue. Thanks!
⋅ October 22, 2019
Hello, Jamil,
Thank you for writing to us.
After taking some time to research the problem, it seems Angular 8.2.11 experiences difficulties when attempting to generate ES5 bundles for differential loading.
We kindly suggest setting the target property of compilerOptions to es5 in the tsconfig.json file.
Would such a solution work for your case?
Looking forward to your reply.
Best Regards,
Vera
⋅ October 28, 2019
Hello Vera,
Thank you for taking your time and review this issue.
As far as I have understood, the solution that you have suggested is related to disabling the "Differential Loading" feature of Angular 8. We have already tried that and understand that, while it is certainly a solution, it also means that, we will not be able to use this feature in whole application.
We were interested to know if there is any plan in near future to make flexmonster compatible with Angular 8 with differential loading feature on.
Looking forward to hearing from you soon.
Humble Regards,
Jamil.
⋅ October 29, 2019
Hello, Jamil,
Thank you for giving us some time.
Our team has tested the case using the latest release of Angular.
With the latest Angular release the normal build (ng build) completes successfully, however, the production build (ng build --prod) hangs on "Differential loading".
An interesting remark is that in Angular 8.1.3 both builds work fine.
We do plan to make Flexmonster compatible with Angular 8 latest release with differential loading feature on.
At the moment, it looks to us like an issue on Angular's side and we await for further Angular updates while continuing to investigate further.
We will notify you in case of any progress on the matter.
Currently, we kindly suggest the following workarounds:
1) Turning the "Differential Loading" feature off
2) Using an earlier release of Angular (for example, v8.1.3), where differential loading completes successfully.
3) Building the project without --prod
You are welcome to contact us in case of questions.
Best Regards,
Vera
