Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) from Joe Pea on 2017-10-01 (public-webapps-github@w3.org from October 2017)

From: Joe Pea <notifications@github.com>
Date: Sun, 01 Oct 2017 05:27:18 +0000 (UTC)
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/587/333354673@github.com>

@robdodson that's an interesting trick. I did something else: I changed arrows to functions, and put the `class` definition inside an `eval()` and it worked that way without causing syntax errors.

But I have another problem: Apparently this all works great with Babel's ES5 output, but I get errors with Buble's ES5 output (I'm using Buble to transpile my lib). I decided not to muck with it for now and support Edge 13+, and maybe by the time the lib I'm making is actually ready for anything serious this adapter won't be needed anymore! 😆

-- 
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-333354673

Received on Sunday, 1 October 2017 05:27:40 UTC