
tanstack-start-server-only
by wodsmith
SKILL.md
name: tanstack-start-server-only description: | TanStack Start server-only patterns using createServerOnlyFn and cloudflare:workers env access. Use when: accessing Cloudflare environment variables (APP_URL, STRIPE_SECRET_KEY, etc.), creating server-only utility functions, working with Stripe or other server-only APIs, or when you need to ensure code only runs on the server and throws if called from client. Covers createServerOnlyFn vs createServerFn differences, env access patterns, and centralized server-only utilities.
TanStack Start Server-Only Patterns
Core Concepts
createServerOnlyFn vs createServerFn
createServerFn: Creates RPC functions callable from client, executes on servercreateServerOnlyFn: Creates functions that ONLY run on server, throws if called from client
Use createServerOnlyFn for:
- Utility functions that access
cloudflare:workersenv - Functions that should never be exposed to client code
- Shared server-side helpers (database access, external APIs)
Environment Variable Access
ALWAYS use env from cloudflare:workers for environment variables in wodsmith-start:
import {env} from 'cloudflare:workers'
// Access bindings and env vars
env.DB // D1 database
env.KV_SESSION // KV namespace
env.R2_BUCKET // R2 bucket
env.APP_URL // Environment variable
env.STRIPE_SECRET_KEY // Secret
NEVER use process.env - it doesn't work in Cloudflare Workers runtime.
TypeScript not recognizing env vars? If you've added new bindings in alchemy.run.ts and deployed with pnpm alchemy:dev, but TypeScript doesn't see them, run:
pnpm cf-typegen
This regenerates worker-configuration.d.ts from wrangler.jsonc to update the type definitions.
Patterns
Centralized Server-Only Utilities
Create shared utilities in src/lib/ using createServerOnlyFn:
// src/lib/env.ts
import {createServerOnlyFn} from '@tanstack/react-start'
import {env} from 'cloudflare:workers'
export const getAppUrl = createServerOnlyFn((): string => {
return env.APP_URL || 'https://wodsmith.com'
})
export const getStripeClientId = createServerOnlyFn((): string | undefined => {
return env.STRIPE_CLIENT_ID
})
Using Server-Only Functions
Import and call directly - no dynamic imports needed:
// In server-fns, route loaders, or other server code
import {getAppUrl} from '@/lib/env'
import {getStripe} from '@/lib/stripe'
export const myServerFn = createServerFn({method: 'POST'}).handler(async () => {
const appUrl = getAppUrl() // Safe - throws if called from client
const stripe = getStripe()
// ...
})
Server-Only API Clients
Wrap API clients in createServerOnlyFn:
// src/lib/stripe.ts
import {createServerOnlyFn} from '@tanstack/react-start'
import {env} from 'cloudflare:workers'
import Stripe from 'stripe'
let stripeInstance: Stripe | null = null
export const getStripe = createServerOnlyFn(() => {
if (stripeInstance) return stripeInstance
if (!env.STRIPE_SECRET_KEY) {
throw new Error('Missing STRIPE_SECRET_KEY')
}
stripeInstance = new Stripe(env.STRIPE_SECRET_KEY, {
apiVersion: '2025-02-24.acacia',
httpClient: Stripe.createFetchHttpClient(),
})
return stripeInstance
})
Server-Only Business Logic
Group related server-only functions:
// src/server/stripe-connect/accounts.ts
import {createServerOnlyFn} from '@tanstack/react-start'
import {getDb} from '@/db'
import {getAppUrl, getStripeClientId} from '@/lib/env'
import {getStripe} from '@/lib/stripe'
export const createExpressAccount = createServerOnlyFn(
async (teamId: string, email: string, teamName: string) => {
const db = getDb()
const stripe = getStripe()
const appUrl = getAppUrl()
// ... implementation
},
)
export const getOAuthAuthorizeUrl = createServerOnlyFn(
(teamId: string, teamSlug: string, userId: string, csrfToken: string) => {
const clientId = getStripeClientId()
const appUrl = getAppUrl()
// ... implementation
},
)
Import Rules
Safe Top-Level Imports
These can be imported at the top of any file:
@tanstack/react-start- Framework utilities includingcreateServerOnlyFn@/lib/env- Server-only env utilities (usescreateServerOnlyFn)@/lib/stripe- Server-only Stripe client (usescreateServerOnlyFn)@/server/*- Server-only business logic (usescreateServerOnlyFn)zod- Validation schemas@/db/schema- Schema type definitions
Why This Works
createServerOnlyFn is processed by a compiler plugin that:
- In server context: Returns the actual function
- In client context: Returns a function that throws an error
This means imports are safe - the function definition exists in both contexts, but execution is blocked on client.
File Organization
src/
├── lib/
│ ├── env.ts # Centralized env access (getAppUrl, getStripeClientId)
│ └── stripe.ts # Stripe client (getStripe)
├── server/
│ └── stripe-connect/
│ ├── accounts.ts # Server-only Stripe Connect functions
│ └── index.ts # Re-exports
└── server-fns/
└── *.ts # createServerFn RPCs that use server-only utilities
Common Mistakes
Wrong: Using process.env
// BAD - doesn't work in Cloudflare Workers
const appUrl = process.env.APP_URL
Wrong: Inline env access everywhere
// BAD - duplicated, no centralization
import {env} from 'cloudflare:workers'
const appUrl = env.APP_URL || 'https://wodsmith.com'
Right: Centralized server-only utilities
// GOOD - centralized, type-safe, server-only enforced
import {getAppUrl} from '@/lib/env'
const appUrl = getAppUrl()
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です