-
Notifications
You must be signed in to change notification settings - Fork 17
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
hmr #2
Comments
Hi @aruntk, can you give me some insight with something? I'm the mantainer of a similar loader but instead of using parse5, it directly uses vulcanize. I encountered the same problem with the downgrading of custom elements. If you have resolved it (the README file points it out) could you explain me how did you done it? |
@aitoroses Hot code reload works now(reload on element file change). I'vent yet figured out how to implement hot module reload. I think as of now it is not possible to implement a complete element = module re-rendering since there is no way to unregister a custom element (afaik). Instead what I'm trying to implement is a partial re-rendering (functions, inner html and property values). I hope it'll lead to a near complete re-rendering. To implement this I might be using https://github.com/Polymer/polymer-analyzer. |
unregister component feature might be needed. WICG/webcomponents#152
The text was updated successfully, but these errors were encountered: