Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)

Here's another dev-related use case:

- I'm building a plugin for an Electron-based app.
- I can't use React, so I thought I'd try web components
- Every time the plugin is reloaded (during development), it throws an exception, as the previous definition still exists
- This means that, instead of HMR, I have to close and reopen the entire app

*yes*, this is a development-related concern. 
*however*, as I like to say, "DX is UX". The experience of your developers just is _a_ user experience, as developers are also users. (mind-blown emoji). 

And DX, like any other UX, strongly determines adoption. 

All I need to be happy here is the ability to mutate an entry in the registry -- no 'unloading' logic, just good ol' idempotence.

But because I can't get it, I think I'm stuck with CSS classes.  

Web components, we had a good 7 minute run



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

Message ID: <WICG/webcomponents/issues/754/1175618768@github.com>