Patrick Nelson

Just wanted to confirm here that I think I have this fully resolved, however my code is very dirty at the moment, so it's **not ready** for a real PR...

**Good news:** I've fixed this issue in version 0.0.8 of my fork of this package: [`svelte-retag`](https://github.com/patricknelson/svelte-retag). 🎉 **Notes:** * Note that `svelte-retag` is still a WIP and so things could...

Update: `svelte-retag` now also supports loading compiled as `iife` and will proactively render your svelte components on-the-fly as the browser parses through your custom elements on page load. This means...

Sweet @Vanillabacke. There's a demo now here too: https://svelte-retag.vercel.app/ Migration should be easy, `svelte-retag`'s API is backward compatible with `svelte-tag` (and will remain that way for version 1). That plus...

Thanks @crisward that's a great workaround! Should be particularly useful in situations where I might end up mixing both `iife` compiled and `es` compiled components. 🤔 Yeah, `display: none` takes...

🤦‍♂️ D'oh! I think I just figured it out. I think me writing this issue was like talking to a rubber duck.🦆 Turns out it's useful for default slots but...

Alright, just reopening for now since technically this issue is still present. Setup PR #15 to address this hopefully once and for all 😅

p.s. While I'm certain this is the correct thing to do moving forward, it _might_ be worth discussing the potential that this could be a breaking change for some folks...

Fixed in _forked_ package: [`svelte-retag`](https://github.com/patricknelson/svelte-retag) Keeping issue + PR open since it's technically still an issue here (in case you still want to merge) 😊

For folks who are using `watchify` in conjunction with `gulp`, you might also consider trying [gulp-bro](https://github.com/ngryman/gulp-bro). I had a similar issue here where update events weren't firing predictably when using...