I'm aware this may not be the right place to post this, and I am sorry for that if so, but using stackoverflow doesn't feel right neither.
I'm very amazed with what esbuild does and love it.
My current build config is --target=chrome58,firefox57,safari11,edge16 and I need large browser compatibility.
But with this target, I can't use destructuring. This is a terrible constraint for anyone like me used to writing code this way.
[0] ✘ [ERROR] Transforming destructuring to the configured target environment ("chrome58", "edge16", "firefox57", "safari11") is not supported yet
But what gives me hope is the "yet". Is it forecasted any how? The roadmap doesn't seem to mention it any how. Nor did the issues.
What suprises me the most is that it doesn't seem too hard to "babelize" (compared to boilerplating await/async behavior for instance).
Or did I miss something?
Thanks for reading
I'm aware this may not be the right place to post this, and I am sorry for that if so, but using stackoverflow doesn't feel right neither.
I'm very amazed with what esbuild does and love it.
My current build config is
--target=chrome58,firefox57,safari11,edge16and I need large browser compatibility.But with this target, I can't use destructuring. This is a terrible constraint for anyone like me used to writing code this way.
But what gives me hope is the "yet". Is it forecasted any how? The roadmap doesn't seem to mention it any how. Nor did the issues.
What suprises me the most is that it doesn't seem too hard to "babelize" (compared to boilerplating
await/asyncbehavior for instance).Or did I miss something?
Thanks for reading