Installation
Install the required dependencies:Configuration
Configuration Options
Properties
bindings: Cloudflare bindings (KV, R2, D1, etc.)entrypoint: Worker entrypoint path- Default:
.svelte-kit/cloudflare/_worker.js
- Default:
assets: Static assets directory- Default:
.svelte-kit/cloudflare
- Default:
compatibilityDate: Cloudflare compatibility date- Minimum:
2024-09-23(required fornodejs_compat)
- Minimum:
compatibilityFlags: Additional compatibility flags- Default:
["nodejs_compat"]
- Default:
Accessing Bindings
Access Cloudflare bindings in your SvelteKit application:Server Load Functions
Server Actions
API Routes
Local Development
SvelteKit provides excellent local development support:- Emulated Cloudflare
platform.envbindings - Hot module replacement
- Fast refresh
Node.js Compatibility
The SvelteKit resource automatically enablesnodejs_compat compatibility flag, which provides:
- Node.js built-in modules (
fs,path,crypto, etc.) - Support for npm packages that depend on Node.js APIs
- Full SvelteKit feature compatibility
Minimum Compatibility Date
Fornodejs_compat support, the compatibility date must be >= 2024-09-23:
TypeScript Configuration
Configure TypeScript for Cloudflare platform types:Deployment Best Practices
- Keep
.svelte-kitdirectory in.gitignore - Use environment variables for secrets via
alchemy.secret.env.X - Test bindings locally using SvelteKit’s platform proxy
- Configure proper TypeScript types for platform bindings
Related Resources
- Website - Base resource for web applications
- D1 Database - SQL database
- KV Namespace - Key-value storage
- R2 Bucket - Object storage