in Version 2.2.0 syntax error occurs in IE11 #1913

RonnyWeiss · 2021-01-29T08:35:33Z

Hello tried the ne version also in IE11 and syntax error occurs!

Would you please fix that?

Kind regards

Ronny

michkami · 2021-01-29T09:15:51Z

I updated to 2.2.0 in my local angular 8 project and had no syntax errors in IE11 yet.

RonnyWeiss · 2021-01-29T10:30:12Z

I use this file:

and got the error in ie can you please check that:

RonnyWeiss · 2021-01-29T10:30:37Z

i just use an other file name :-)

RonnyWeiss · 2021-01-29T10:32:46Z

in full file the error occurs in line 20,21

netil · 2021-02-01T03:04:44Z

Hi @RonnyWeiss, the issue comes from Webpack v5, where webpack's runtime code uses ES2015 syntax.

After adding config option to transpile for older browser, looks working fine.
I'll be release the patch version soon.

As of Webpack v5 transpile using ES6 syntax, needs to add extra target configuration to support old browser. https://webpack.js.org/migrate/5/#need-to-support-an-older-browser-like-ie-11 Ref naver#1913

## [2.2.1](2.2.0...2.2.1) (2021-02-01) ### Bug Fixes * **build:** suport for legacy browser ([594d18e](594d18e)), closes [/webpack.js.org/migrate/5/#need-to-support-an-older-browser-like-ie-11](https://github.com//webpack.js.org/migrate/5//issues/need-to-support-an-older-browser-like-ie-11) [#1913](#1913) * **gauge:** units position if fullCircle ([62cd79e](62cd79e)), closes [#1914](#1914)

RonnyWeiss · 2021-02-01T07:46:18Z

Thank you very much. :-)

netil added the bug label Feb 1, 2021

netil mentioned this issue Feb 1, 2021

fix(build): suport for legacy browser #1915

Merged

netil closed this as completed in 594d18e Feb 1, 2021

Provide feedback