Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

@rniwa thanks for mentioning me but I'm not sure it's so easy.

[Babel is plain broken](https://github.com/babel/babel/issues/4480) when it comes to super calls and my poly already patches `HTMLELement`, so does the one from googlers.

I strongly believe this should be solved on Babel side, otherwise we're blocking and degrading native performance because of tooling on our way.

Tooling should improve and help, not be a problem.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/587#issuecomment-254144357