If you have to support IE compatibility with this plugin, then I think using Babel is a good choice. The main reason in IE11 is that it cannot parse es6 syntax (such as arrow function), so a transpiler like Babel is needed to make it work.
Is Babel the only/best way of handling the incompatibility?
As far as I know, Babel works with most front-end frameworks to support site compatibility within IE 11, I think this is because of the advantages of Babel itself that makes it so popular.
发布评论
评论（1）
如果您必须支持IE与此插件的兼容性，那么我认为使用Babel是一个不错的选择。 IE11中的主要原因是它不能解析
es6语法（例如箭头函数），因此需要像babel这样的转板器来使其正常工作。据我所知，Babel与大多数前端框架合作，以支持IE 11中的网站兼容性，我认为这是因为Babel本身的优势使其如此受欢迎。
If you have to support IE compatibility with this plugin, then I think using Babel is a good choice. The main reason in IE11 is that it cannot parse
es6syntax (such as arrow function), so a transpiler like Babel is needed to make it work.As far as I know, Babel works with most front-end frameworks to support site compatibility within IE 11, I think this is because of the advantages of Babel itself that makes it so popular.