Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML imports deprecated: rewrite for Polymer 3 using ES modules and npm #54

Open
pzingg opened this issue Nov 15, 2018 · 2 comments
Open

Comments

@pzingg
Copy link

pzingg commented Nov 15, 2018

The use of Bower and HTML Imports in this repository is already causing usability problems for me.

HTML Imports are deprecated in Chrome M70, and will be removed in M73, around April 2019.
https://www.chromestatus.com/feature/5144752345317376

HTML Imports were never implemented in Firefox, and require polyfills.

The latest version of webcomponentsjs says, "The HTML Imports polyfill has been removed. Given that ES modules have shipped in most browsers, the expectation is that web components code will be loaded via ES modules."

And finally, Polymer version 3 is abandoning HTML imports, and using ES modules instead: https://www.linkedin.com/pulse/writing-web-components-from-future-polymer-3-rafa-bernad

I am really a novice at Web Components, but is this an easy migration?

@pzingg
Copy link
Author

pzingg commented Nov 16, 2018

I guess the other thing to mention is that the current version seems to require the Custom Elements v0 polyfill (webcomponentsjs version 0.7.24 or earlier). I think at a minimum, the code here should work with the more stable and accepted Custom Elements v1 API and polyfill.

I also found that handsontable itself will not compile with the Polymer 3 CLI ("polymer serve") because of missing "default export" clauses and external dependencies that aren't ES-module conformant, like pikaday...

@AMBudnik
Copy link

Thank you for sharing the proposition and tracking down the changes that are needed to update the project to Polymer 3. That would surely benefit us all. We haven't had time to update it yet, but as our CTO says

web components are the future

so I believe that we will be able to get our hands on that subject in 2019.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants