next-evolve 0.3.4 → 0.3.5

package/README.md

@@ -6,9 +6,9 @@ A/B tests and bandits for Next.js App Router sites. Variants are chosen on the s
 
 **Requirements:** Next.js 15.5 or newer with the App Router, Node 22.12 or newer, a Postgres 14+ database, and a host that runs a Node server (not `output: "export"`).
 
-## Quickstart (about 10 minutes)
+## Quickstart (about 15 minutes)
 
-This gets you from an existing Next.js app to a running experiment in local development.
+This gets you from an existing Next.js app to a running experiment in local development. A timed run on a fresh `create-next-app` reached a variant served, an exposure recorded and the visitor in the dashboard in under 6 minutes.
 
 ### 1. Create a site
 
@@ -19,7 +19,7 @@ Sign in at [app.evolveab.com](https://app.evolveab.com), enter a site name and c
 Evolve writes events into its own `evolve` schema, so your app's existing database is fine. For local development, Docker works:
 
 ```sh
-docker run -d --name evolve-pg -e POSTGRES_PASSWORD=postgres -p 54329:5432 postgres:17
+docker run -d --name evolve-pg -e POSTGRES_PASSWORD=postgres -p 54320:5432 postgres:17
 ```
 
 For production, any Postgres works (Neon, Supabase, RDS, your own). On serverless hosts use the pooled URL (for example Neon's `-pooler` host).
@@ -32,7 +32,7 @@ In your app's directory:
 npx next-evolve init \
   --key evk_live_… \
   --webhook-secret whsec_… \
-  --db postgres://postgres:postgres@localhost:54329/postgres \
+  --db postgres://postgres:postgres@localhost:54320/postgres \
   --routes "/"
 ```
 

package/dist/react/region.js

@@ -8,7 +8,7 @@ import { CONTROL_CODE, decodeCode } from "@next-evolve/protocol";
 import { createElement } from "react";
 import { headers } from "next/headers";
 import { unstable_rethrow } from "next/navigation";
-import { after } from "next/server";
+import { after, connection } from "next/server";
 // src/react/region.tsx
 let warnedNoContext = false;
 async function currentCode() {
@@ -100,6 +100,7 @@ async function Optimizable({ id, component, props }) {
 	if (code === CONTROL_CODE) return control();
 	const pairs = decodeCode(code);
 	if (!pairs || pairs.length === 0) return control();
+	if (!requestContext().code) await connection();
 	let bundle = await getRenderBundle();
 	let hit = findPair(bundle, pairs, id);
 	const unknown = () => pairs.some((p) => !bundle?.variants[p.var]);

package/docs/troubleshooting.md

@@ -15,7 +15,7 @@ Start with `npx next-evolve doctor`. It checks the env, key, database, bundle, p
 **`cacheComponents` errors.**
 - `Route segment config "revalidate" is not compatible with nextConfig.cacheComponents`: the page was set up in static mode. Re-run `npx next-evolve init` with `next-evolve` 0.3.4 or newer (it uses dynamic mode with `cacheComponents`), or by hand: move the page back out of `app/[evolve]/`, remove the `withEvolve`/`evolveStaticParams`/`evolveMetadata` lines and set the route's mode to `"dynamic"`.
 - `uncached or runtime data … accessed outside of <Suspense>` in `next build`: wrap `<Optimizable>` in `<Suspense>`.
-- `encountered the unstable value Date.now()` in the dev overlay, pointing at `<Optimizable>`: upgrade to `next-evolve` 0.3.4 or newer.
+- `encountered the unstable value Date.now()` in the dev overlay, pointing at `<Optimizable>`: upgrade to `next-evolve` 0.3.5 or newer.
 
 **`doctor`: "Database: not migrated".** Run `npx next-evolve migrate`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-evolve",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "description": "Self-improving Next.js sites: server-side variants with no flicker, measured in your own Postgres.",
   "license": "MIT",
   "type": "module",