José Pablo Ramírez Vargas

Hello, @kwangure and thanks for dropping by. It seems that isolation in browsers is based on the context, and since this is all in the same window, same document, there...

Anyway, by extending the logic, it seems that externalizing the "svelte" module alone is not sufficient to do the trick. At this point I would absolutely loved it if core...

My uneducated alternatives are, in my mind: 1. Correct whatever needs correction so the Svelte runtime can be de-duped and all state from all MFE's use the same reactive graph....

Hello again, @kwangure. I hadn't realized that `root` had lost reactivity after I introduced externalization. My oversight. Thanks for pointing it out. The plug-in `vite-plugin-externalize-dependencies` (or similar ones) are only...

Yes, it would be great if that Vite issue could be implemented for sure for **development** mode. But that leaves us with the **lifecycle_outside_component** error when the projects are built...

Hello, @paoloricciuti and thanks for the note. I'll maybe try a thing or two out, but in all honesty, that looks very scary! Hehe. Even if I could mount a...

Note that some previous change (which may be the one being referred to here) broke @testing-library/svelte's TypeScript support. I mention this here because perhaps it could be verified.

Generally speaking, what's supposed to happen in a case like the following? + Component A sets title. Backs up previous title => backupA. + Component B loads and sets new...

I think the solution to my proposed scenario would be to centralize the "history" of backups. The owner, which will be at the top of the history stack, will pop...

Assuming my proposal is carried into reality, here's another scenario: + Component A + Component B + Component C At this point, say all 3 components are loaded and they...