I would state that Angular is not the best solution if you have to support IE 11 then. For whatever reason you still have to support IE11 (enterprise maybe?), using modern frameworks with it is never an ideal solution, so going back to something more easier would be probably the way to go then.
I'm actually going to disagree. It was still possible to support IE11, fully, despite the polyfills and ponyfills.
Knowing the limitations now allows us to move forward keeping these restrictions in mind, but Angular on its own is not to fault, and potentially shouldn't be overlooked just because IE11 has to be supported.
It also allows us to continue to develop in a modern environment, which keeps the option that if we ever no longer have to support IE11, due to changes in SLAs, then we can remove the polyfills and alter the target in the tsconfig compilerOptions to target a more modern version of ECMAScript.
I've worked on a few apps with Angular that support IE11, had no issues that were Angular specific. Also with Angular 8 there's differential loading which produces polyfill bundles for older browsers alongside smaller bundles for modern browsers (it's very clever!)
It is, I have a note in the article how it can increase bundle size if you allow it to run for IE9 and 10.
From what I've experienced though, was that dropping the target to es5 meant that your dependencies have to support es5.
I left a comment under one of the feedback to this article to state that it was very possible to support IE11, and in truth, Angular did not in itself have any issues, however, the additional tools you might use along with it will need extra work
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would state that Angular is not the best solution if you have to support IE 11 then. For whatever reason you still have to support IE11 (enterprise maybe?), using modern frameworks with it is never an ideal solution, so going back to something more easier would be probably the way to go then.
I'm actually going to disagree. It was still possible to support IE11, fully, despite the polyfills and ponyfills.
Knowing the limitations now allows us to move forward keeping these restrictions in mind, but Angular on its own is not to fault, and potentially shouldn't be overlooked just because IE11 has to be supported.
It also allows us to continue to develop in a modern environment, which keeps the option that if we ever no longer have to support IE11, due to changes in SLAs, then we can remove the polyfills and alter the target in the tsconfig compilerOptions to target a more modern version of ECMAScript.
I've worked on a few apps with Angular that support IE11, had no issues that were Angular specific. Also with Angular 8 there's
differential loadingwhich produces polyfill bundles for older browsers alongside smaller bundles for modern browsers (it's very clever!)It is, I have a note in the article how it can increase bundle size if you allow it to run for IE9 and 10.
From what I've experienced though, was that dropping the target to es5 meant that your dependencies have to support es5.
I left a comment under one of the feedback to this article to state that it was very possible to support IE11, and in truth, Angular did not in itself have any issues, however, the additional tools you might use along with it will need extra work