José Pablo Ramírez Vargas

> This problem seems to affect components that receive optional snippets (perhaps the "optional" part is not required for reproduction): > > ```svelte > > import Other from './Other.svelte'; //...

Although @KieranP seems to be after $effect() for the wrong reasons on this particular instance, I'm with him in that $effect() should accept async functions. I know, this was removed...

If I remember correctly, back in the day when the types for `$effect` allowed async functions, the documentation stated very clearly what was tracked: "and up to the first await.",...

Is not that $effect disallows async functions, is that its TypeScript has been made not to take it. If you ignore the TS error and write async code in your...

And the expectation here would be for all reactive signals to account for effect re-run and derived value recalculation, even the ones read after awaiting? Otherwise it would be identical...

> if you update the typings to accept an async function (btw i think we should not do such thing) but don't await the function when running the effect they...

Hello. It is not a typo. It merely was how it was in earlier versions of the plug-in. I just submitted PR #639 to update the docs to v0.7.0. You...

Use [@wjfe/single-spa-svelte](https://github.com/WJSoftware/wjfe-single-spa-svelte).

Thanks for dropping by! I tried doing what one would do for React: Import Svelte from a CDN and mark it **external** in Vite. This of course, requires that the...

Ok, I think I successfully set the project up for de-duplication of Svelte using unpkg.com. It is the same repository, but in the branch named **JP/SvelteExternalized**. The project runs fine...