Skip to content

[FSSDK-12647] doc update #338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
junaed-optimizely merged 1 commit into from
May 18, 2026
Merged

[FSSDK-12647] doc update #338

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -594,15 +594,14 @@ The React SDK supports server-side rendering (SSR). A pre-fetched datafile is re

#### Per-request client

Create a client inside the component with a pre-fetched datafile. Use `useState` with a lazy initializer to create the instance once. On the server, use `createStaticProjectConfigManager` with `disposable: true` so the instance can be garbage collected without explicitly calling `close()`. On the client, use `createPollingProjectConfigManager` to keep the datafile up to date.
Create a client inside the component with a pre-fetched datafile. Use `useState` with a lazy initializer to create the instance once. Pass the datafile for immediate readiness during server rendering, and set `disposable: true` on the server so the instance can be garbage collected without explicitly calling `close()`.

```tsx
'use client';

import { useState } from 'react';
import {
createInstance,
createStaticProjectConfigManager,
createPollingProjectConfigManager,
createBatchEventProcessor,
OptimizelyProvider,
Expand All @@ -615,13 +614,11 @@ export default function Page({ datafile, userId }) {

const [optimizely] = useState(() =>
createInstance({
projectConfigManager: isServerSide
? createStaticProjectConfigManager({ datafile })
: createPollingProjectConfigManager({
sdkKey: process.env.NEXT_PUBLIC_OPTIMIZELY_SDK_KEY || '',
datafile,
}),
eventProcessor: isServerSide ? undefined : createBatchEventProcessor(),
projectConfigManager: createPollingProjectConfigManager({
sdkKey: process.env.NEXT_PUBLIC_OPTIMIZELY_SDK_KEY || '',
datafile,
}),
eventProcessor: createBatchEventProcessor(),
defaultDecideOptions: isServerSide ? [OptimizelyDecideOption.DISABLE_DECISION_EVENT] : [],
disposable: isServerSide,
})
Expand Down
13 changes: 5 additions & 8 deletions docs/nextjs-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,6 @@ Since `OptimizelyProvider` uses React Context (a client-side feature), it must b
import {
OptimizelyProvider,
createInstance,
createStaticProjectConfigManager,
createPollingProjectConfigManager,
createBatchEventProcessor,
OptimizelyDecideOption,
Expand All @@ -109,13 +108,11 @@ export function OptimizelyClientProvider({ children, datafile }: { children: Rea

const [optimizely] = useState(() =>
createInstance({
projectConfigManager: isServerSide
? createStaticProjectConfigManager({ datafile })
: createPollingProjectConfigManager({
sdkKey: process.env.NEXT_PUBLIC_OPTIMIZELY_SDK_KEY || '',
datafile,
}),
eventProcessor: isServerSide ? undefined : createBatchEventProcessor(),
projectConfigManager: createPollingProjectConfigManager({
sdkKey: process.env.NEXT_PUBLIC_OPTIMIZELY_SDK_KEY || '',
datafile,
}),
eventProcessor: createBatchEventProcessor(),
defaultDecideOptions: isServerSide ? [OptimizelyDecideOption.DISABLE_DECISION_EVENT] : [],
disposable: isServerSide,
})
Expand Down
Loading