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
ManagedRuntimewindow.documentWhat 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- Using fiber refs and use
Effect.locally- 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
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
