Andrea Giammarchi
1 min readJul 12, 2019

--

Just to clarify … this whole post is about people targeting ES5. There are various follows up about not targeting ES5 and differentiating the target, and I’ve written one, you suggested another one, other wrote others too.

Yet, this post is about people targeting ES5, so saying if you don’t target ES5 it’s better, it’s surely correct, but here I wanted to explain why libraries authors, that cannot know what their users target, and developers targeting ES5, should pay attention to what they write.

Not targeting ES5 is a solution? Sure thing, but here it’s about those devs targeting ES5 or having no clue where their code will run, after which bundler, env, or toolchain.

--

--

Andrea Giammarchi
Andrea Giammarchi

Written by Andrea Giammarchi

Web, Mobile, IoT, and all JS things since 00's. Formerly JS engineer at @nokia, @facebook, @twitter.

Responses (1)