Contents

Not released yet. The React and Next.js SDK for e-volv Launch is built and conformance-tested, but its first release with flags is not on the registry yet. This page documents that release: until it ships, npm install @e-volv/logs react finds either nothing or an earlier Observer-only version without flags. The SDKs index shows what can be installed today.

React hooks and Next.js helpers

Bootstrap Launch flags in React without a first-render flash and evaluate them in Next.js middleware.

How it works

  • EvolveFlagsProvider accepts a browser flags client or a client key and optional server bootstrap values.
  • useFlag returns the current value. useFlagDetail adds variant and reason. Updates subscribe through useSyncExternalStore.
  • Each provider caches a value per key, so a key records one exposure per provider until it changes, not one per re-render or per component that reads it. Server-rendered bootstrap values record none.
  • getServerFlags creates the bootstrap object on the server from flags marked client-side available, without recording exposures. flagsMiddleware forwards a snapshot as a request header for flag-based redirects; with the edge client, pass the keys to forward. A snapshot over 4 KB is not forwarded.
import { EvolveFlagsProvider, useFlag } from '@e-volv/logs/react';

function Checkout() {
  const enabled = useFlag('checkout.new', false);
  return enabled ? <NewCheckout /> : <Checkout />;
}

Read the Launch overview or the SDK guides.

We use only essential cookies to keep you signed in and the app working. With your consent we may enable optional analytics to help us improve e-volv. See our Privacy Policy and Terms.