IE 11 error

Hello,
 
Thank you for reporting the issue.
 
We want to explain that our wrapper for Angular uses the ES6 version of Flexmonster.
Being incompatible with IE, ES6 standard leads to the error.
We suggest modifying our wrapper in the way it uses ES5 instead of the default ES6 version.
The wrapper's source code can be found on our GitHub.
The following line of code is responsible for importing Flexmonster. Please replace the path with the following string: flexmonster/flexmonster.es5.full.
 
Also, please note that this wrapper should be embedded in your project manually instead of installing it through npm.
 
Please let us know if it works for you.
 
Best regards,
Illia

Hello,
 
Thank you for giving us some time.
 
Currently, the Angular wrapper for Flexmonster is installed as an npm module in your project. In order to make it use the ES5 version of the component, it needs to be embedded in your project manually instead of using it as an npm module.
 
It means this wrapper can be removed from your npm dependencies.
Instead, download the wrapper's source code from our GitHub.
Next, modify the import statement in the flexmonster.component.ts file as shown below:

import { Component, ElementRef, Input, Output, EventEmitter } from '@angular/core';
import * as Flexmonster from 'flexmonster/flexmonster.es5.full';

@Component({
  selector: 'fm-pivot',
  template: '<div><div class="fm-ng-wrapper"></div></div>'
})

...

 
We have prepared a sample Angular project to demonstrate this approach. It can be found in attachments.
In this example, flexmonter.component.ts and flexmosnter.module.ts are embedded directly into the src/app folder of the application.
 
Please let us know if it works for you.
Our team is looking forward to hearing your feedback.
 
Best regards,
Illia

Hello,
 
Thank you for your feedback.
 
Our team would like to notice that in this case, the wrapper needs to be updated manually. Yet, we want to notice that the Angular wrapper does not receive significant updates every minor release. Further versions of the component are likely to be compatible with older versions of the wrapper.
 
Even so, we understand your concerns on this point. Our team agrees that the possibility to use our npm package with the ES5 version of the component sounds reasonable.
Therefore we have added this request to our backlog.
 
We will notify you in case something is changed on this point.
 
Feel free to reach out in case any further questions arise.
 
Best regards,
Illia

Hello,
 
Thank you for your feedback.
 
We want to notice that the ECMAScript standard does not affect the functionality of the component.
The same list of features is available both for ES5 and ES6 Flexmonster's versions.
 
Feel free to contact us in case any further questions arise.
 
Regards,
Illia