You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/integrating-with-flagsmith/sdks/client-side-sdks/nextjs-and-ssr.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ An example application for Next.js middleware can be found
23
23
### NPM
24
24
25
25
```bash
26
-
npm i flagsmith --save
26
+
npm i @flagsmith/flagsmith --save
27
27
```
28
28
29
29
## Basic Usage
@@ -34,7 +34,7 @@ settings page.
34
34
## Comparing SSR and client-side Flagsmith usage
35
35
36
36
The SDK is initialised and used in the same way as the [JavaScript](/integrating-with-flagsmith/sdks/client-side-sdks/javascript) and [React](/integrating-with-flagsmith/sdks/client-side-sdks/react)
37
-
SDK. The main difference is that Flagsmith should be imported from `flagsmith/isomorphic`.
37
+
SDK. The main difference is that Flagsmith should be imported from `@flagsmith/flagsmith/isomorphic`.
38
38
39
39
The main flow with Next.js and any JavaScript-based SSR can be as follows:
40
40
@@ -56,9 +56,9 @@ state. Below is an example for the **app** router as well as the **pages** route
0 commit comments