SvelteKit
A user-friendly guide to integrate the React-based Capsule Modal into your SvelteKit application.
This guide details how to integrate the Capsule Modal—originally built in React—into your SvelteKit application.
Although mixing React and Svelte is unusual, we can do so via svelte-preprocess-react. If you prefer to build your own custom UI, you can also use @usecapsule/web-sdk
directly.
If you haven’t already you can create a new SvelteKit project by following the official SvelteKit docs. Alternatively, you can fork our minimal starter that already includes the Capsule Modal setup: Capsule Nuxt 3 Starter.
Prerequisites
To use Capsule, you need an API key. This key authenticates your requests to Capsule services and is essential for integration.
Don’t have an API key yet? Request access to the Developer Portal to create API keys, manage billing, teams, and more.
Installing Dependencies
Install the Capsule React SDK, plus React dependencies:
Configuring SvelteKit (Preprocessor & Polyfills)
Svelte Preprocess React
In your svelte.config.js, import and apply svelte-preprocess-react
:
Vite Plugins (Node Polyfills)
SvelteKit uses Vite under the hood. Install and configure polyfills for Node modules:
Then enable it in vite.config.ts
:
If you prefer SSR, ensure you dynamically handle the React-based modal on the client. If you want pure client-side
usage, set export const ssr = false;
in your page’s .ts
or .js
files for SvelteKit to skip SSR.
Setting Up the Capsule SDK
Now that you’ve installed the necessary dependencies, let’s set up the Capsule SDK in your SvelteKit application. This involves creating a client instance and integrating the Capsule Modal.
Creating a Capsule Client Instance
As with other frameworks, you’ll need a dedicated file for your client instance (e.g., client/capsule.ts
):
Capsule offers two hosted environments: Environment.BETA
(alias Environment.DEVELOPMENT
) for
testing, and Environment.PROD
(alias Environment.PRODUCTION
) for live use. Select the
environment that matches your current development phase.
Using the Capsule Modal in a SvelteKit Route
Let’s say you have a +page.svelte
in src/routes/
. You would use the Capsule Modal with the preprocessed React component:
With SSR disabled, the page will be served client-side only, ensuring the React-based modal can load without conflicts.
Beta Testing Credentials
In the BETA
Environment, you can use any email ending in @test.usecapsule.com
(like dev@test.usecapsule.com) or US phone numbers (+1) in the format (area code)-555-xxxx
(like (425)-555-1234). Any OTP code will work for verification with these test credentials.
These credentials are for beta testing only. You can delete test users anytime in the beta developer console to free up user slots.
Customizing the Capsule Modal
Just like in React, you can provide any additional props to the <CapsuleModal>
component. For example, customizing
theming:
If You Don’t Want to Use the React Modal
Use `@usecapsule/web-sdk` to build your own SvelteKit-based UI from scratch. This approach avoids mixing React entirely. For details on how to do this, refer to the Customize Capsule guide.
Examples
We have a dedicated SvelteKit Capsule SvelteKit Starter demonstrating how to setup the React-based Capsule Modal. Feel free to explore it for a deeper reference.
Next Steps
After integrating Capsule, you can explore other features and integrations to enhance your Capsule experience. Here are some resources to help you get started:
Ecosystems
Learn how to use Capsule with popular Web3 clients and wallet connectors. We’ll cover integration with key libraries for EVM, Solana, and Cosmos ecosystems.
If you’re ready to go live with your Capsule integration, make sure to review our go-live checklist:
Troubleshooting
Integration Support
If you’re experiencing issues that aren’t resolved by our troubleshooting resources, please contact our team for assistance. To help us resolve your issue quickly, please include the following information in your request:
1
A detailed description of the problem you’re encountering.
2
Any relevant error messages or logs.
3
Steps to reproduce the issue.
4
Details about your system or environment (e.g., device, operating system, software version).
Providing this information will enable our team to address your concerns more efficiently.
Was this page helpful?