--- id: proxy-svelte title: Svelte Proxy SDK ---
This library can be used with the [Unleash Proxy](https://github.com/Unleash/unleash-proxy) or with the [Unleash front-end API](../reference/front-end-api). It is _not_ compatible with the regular Unleash client API. For more detailed information, check out the [Svelte Proxy SDK on GitHub](https://github.com/Unleash/proxy-client-svelte). ## Installation ```shell npm2yarn npm install @unleash/proxy-client-svelte ``` ## Initialization Import the provider like this in your entrypoint file (typically index.svelte): ```jsx ``` Alternatively, you can pass your own client in to the FlagProvider: ```jsx ``` ## Deferring client start By default, the Unleash client will start polling the Proxy for toggles immediately when the `FlagProvider` component renders. You can delay the polling by: - setting the `startClient` prop to `false` - passing a client instance to the `FlagProvider` ```jsx ``` Deferring the client start gives you more fine-grained control over when to start fetching the feature toggle configuration. This could be handy in cases where you need to get some other context data from the server before fetching toggles, for instance. To start the client, use the client's `start` method. The below snippet of pseudocode will defer polling until the end of the `asyncProcess` function. ```jsx ``` ## Usage ### Check feature toggle status To check if a feature is enabled: ```jsx {#if $enabled} {:else} {/if} ``` ### Check variants To check variants: ```jsx {#if $variant.enabled && $variant.name === 'SomeComponent'} {:else if $variant.enabled && $variant.name === 'AnotherComponent'} {:else} {/if} ``` ### Defer rendering until flags fetched useFlagsStatus retrieves the ready state and error events. Follow the following steps in order to delay rendering until the flags have been fetched. ```jsx {#if !$flagsReady} {:else} {/if} ``` ### Updating context Follow the following steps in order to update the unleash context: ```jsx ```