distribute as es6

[filipbech]

It seems the package on npm is compiled to es5 before distribution. This is very unfortunate, since it doesn't work in es5 (Chrome requires customElements.define to take a class and not a function).

[ChristophP]

@filipbech Hmm interesting, have you used this dependency on your page?
<script src="https://cdnjs.cloudflare.com/ajax/libs/webcomponentsjs/1.0.1/custom-elements-es5-adapter.js"></script> as mentioned in the readme here?
Distributing as ES6 isn't so easy if you want things to be compatible with IE for example or any non ES6 compliant browser.

[filipbech]

Sorry for the delay (missed the notification apparently)
No, thats right. I missed that in the readme.
Maybe you could distribute both versions? Or at least my opinion would be to describe how to use the polyfills, but not have them as a dependency (as they are hopefully going away more and more)

[ChristophP]

@filipbech Feedback taken. The polyfills are somewhat opaque to the user and also probaby a bit outdated since we first published this library.
I am currently going over this repository to fix some issues that npm audit warns about. While doing that I will be upgrading babel. I will upgrade babel too. I will look for a solution with a babel plugin that does at compile time what custom-elements-es5-adapter.js does at runtime. There was a plugin back when I first wrote this libary but I couldn't get it to work back then.
That solution would be ideal, because then noone would have to care about whether it's ES or ES5. It would just work.
Distributing it as ES6 would be a fallback solution, but wouldn't be great because it comes at the cost of not working in non-ES6 browsers/