Strategies for Handling `ManagedRuntime` in a Svelte Application
I'm using
What are the possible solutions to solve this problem? At the moment these are the solutions that came to my mind:
- Using fiber refs, provide them
- Using fiber refs and use
- Using elements as service tags and provide them locally with
- Split in two managed runtime where the first one is used to create the other and the latter has everything provided
ManagedRuntime on the front-end, specifically a svelte application. Having some services relying on window.document, sdk that must be loaded one time, and so on.What are the possible solutions to solve this problem? At the moment these are the solutions that came to my mind:
- Using fiber refs, provide them
onMount and having them shared in the runtime- Using fiber refs and use
Effect.locally to provide them- Using elements as service tags and provide them locally with
Effect.provideService- Split in two managed runtime where the first one is used to create the other and the latter has everything provided
