Scaffold next-app

Author: rafinutshaw-optimizely

.eslintrc.json

@@ -0,0 +1,3 @@
+{
+  "extends": "next/core-web-vitals"
+}

.gitignore

@@ -0,0 +1,35 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# next.js
+/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# local env files
+.env*.local
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts

README.md

@@ -1 +1,34 @@
-# next-js-starter-kit
+This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
+
+## Getting Started
+
+First, run the development server:
+
+```bash
+npm run dev
+# or
+yarn dev
+# or
+pnpm dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+
+You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
+
+This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.
+
+## Learn More
+
+To learn more about Next.js, take a look at the following resources:
+
+- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
+- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
+
+You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
+
+## Deploy on Vercel
+
+The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
+
+Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

app/components/decision.tsx

@@ -0,0 +1,51 @@
+import { useDecision } from "@optimizely/react-sdk";
+import Pre from "./pre";
+
+interface DecisionType {
+  userId: string;
+  setHasOnFlag: Function;
+}
+
+export const Decision: React.FC<DecisionType> = (props: DecisionType) => {
+  const { userId, setHasOnFlag } = props;
+
+  // Generally React SDK runs for one client at a time i.e for one user throughout the lifecycle.
+  // You can provide the user Id once while wrapping the app in the Provider component and the SDK will memoize and reuse it throughout the application lifecycle.
+  // For this example, we are simulating 10 different users so we will ignore this and pass override User IDs to the useDecision hook for demonstration purpose.
+  // This override will not be needed for normal react sdk use cases.
+  const [decision, clientReady] = useDecision(
+    "product_sort",
+    {},
+    { overrideUserId: userId }
+  );
+
+  // Don't render the component if SDK client is not ready yet.
+  if (!clientReady) {
+    return "";
+  }
+
+  const variationKey = decision.variationKey;
+
+  // did decision fail with a critical error?
+  if (variationKey === null) {
+    console.log(" decision error: ", decision["reasons"]);
+  }
+
+  if (decision.enabled) {
+    setTimeout(() => setHasOnFlag(true));
+  }
+
+  // get a dynamic configuration variable
+  // "sort_method" corresponds to a variable key in your Optimizely project
+  const sortMethod = decision.variables["sort_method"];
+
+  return (
+    <Pre>
+      {`\nFlag ${
+        decision.enabled ? "on" : "off"
+      }. User number ${userId} saw flag variation: ${variationKey} and got products sorted by: ${sortMethod} config variable as part of flag rule: ${
+        decision.ruleKey
+      }`}
+    </Pre>
+  );
+};

app/components/flags-off-message.tsx

@@ -0,0 +1,32 @@
+import Pre from "./pre";
+
+interface FlagsOffMessageType {
+  projectId: string;
+}
+
+export const FlagsOffMessage: React.FC<FlagsOffMessageType> = (
+  props: FlagsOffMessageType
+) => {
+  const { projectId } = props;
+  const navLink = `https://app.optimizely.com/v2/projects/${projectId}/settings/implementation`;
+  return (
+    <div>
+      <Pre>Flag was off for everyone. Some reasons could include:</Pre>
+      <Pre>
+        1. Your sample size of visitors was too small. Rerun, or increase the
+        iterations in the FOR loop
+      </Pre>
+      <Pre>
+        2. By default you have 2 keys for 2 project environments (dev/prod).
+        Verify in Settings{">"}Environments that you used the right key for the
+        environment where your flag is toggled to ON.
+      </Pre>
+      <Pre>
+        Check your key at <a href={navLink}>{navLink}</a>
+      </Pre>
+      <br />
+    </div>
+  );
+};
+
+export default FlagsOffMessage;

app/components/pre.tsx

@@ -0,0 +1,9 @@
+import { PropsWithChildren } from "react";
+
+export const Pre: React.FC<PropsWithChildren> = (props: PropsWithChildren) => {
+  const { children } = props;
+
+  return <pre style={{ margin: 0 }}>{children}</pre>;
+};
+
+export default Pre;

app/globals.css

@@ -0,0 +1,21 @@
+
+*, *::before, *::after {
+  box-sizing: border-box;
+}
+
+* {
+  margin: 0;
+}
+
+body {
+  line-height: 1.5;
+  -webkit-font-smoothing: antialiased;
+}
+
+p, h1, h2, h3, h4, h5, h6 {
+  overflow-wrap: break-word;
+}
+
+#root, #__next {
+  isolation: isolate;
+}

app/layout.tsx

@@ -0,0 +1,22 @@
+import './globals.css'
+import type { Metadata } from 'next'
+import { Inter } from 'next/font/google'
+
+const inter = Inter({ subsets: ['latin'] })
+
+export const metadata: Metadata = {
+  title: 'Create Next App',
+  description: 'Generated by create next app',
+}
+
+export default function RootLayout({
+  children,
+}: {
+  children: React.ReactNode
+}) {
+  return (
+    <html lang="en">
+      <body className={inter.className}>{children}</body>
+    </html>
+  )
+}