- Notifications
You must be signed in to change notification settings - Fork17
vercel/flags
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
The feature flags toolkit for Next.js and SvelteKit.
From the creators of Next.js, the Flags SDK is a free open-source library that gives you the tools you need to use feature flags in Next.js and SvelteKit applications.
- Works with any flag provider, custom setups or no flag provider at all
- Compatible with App Router, Pages Router, and Edge Middleware
- Built for feature flags and experimentation
Seeflags-sdk.dev for full docs and examples.
Install the package using your package manager:
npm install flags
Create an environment variable calledFLAGS_SECRET
.
TheFLAGS_SECRET
value must have a specific length (32 random bytes encoded in base64) to work as an encryption key. Create one using node:
node -e"console.log(crypto.randomBytes(32).toString('base64url'))"
This secret is required to use the SDK. It is used to read overrides and to encrypt flag values in case they are sent to the client and should stay secret.
Create a file called flags.ts in your project and declare your first feature flag there:
// app/flags.tsximport{flag}from'flags/next';exportconstexampleFlag=flag<boolean>({key:'example-flag',decide(){returntrue;},});
Call your feature flag in a React Server Component:
// app/page.tsximport{exampleFlag}from'./flags';exportdefaultasyncfunctionPage(){constexample=awaitexampleFlag();return<div>{example ?'Flag is on' :'Flag is off'}</div>;}
Feature Flags can also be called in Edge Middleware and API Routes.
The Flags SDK has adapters for popular feature flag providers including LaunchDarkly, Optimizely, and Statsig.
There is a lot more to the Flags SDK than shown in the example above.
See the full documentation and examples onflags-sdk.dev.
About
Flags SDK by Vercel