Replace token with your main project token which you can find in the Settings tab of your project.
3. Generate the client
Generate a type-safe client to access your flags by running:
npxhypertune
yarnhypertune
pnpmhypertune
4. Use the client
Install the dotenv package or ensure you have another way to load environment variables:
npminstalldotenvnpminstall-D@types/dotenv
yarnadddotenvyarnadd-D@types/dotenv
pnpmadddotenvpnpmadd-D@types/dotenv
Add a new file called loadEnv.ts that loads environment variables with dotenv:
Add a new file called getHypertune.ts that exports a getHypertune function:
To access flags, use the getHypertune function:
5. (Optional) Include a build-time snapshot
To improve reliability, you can include a snapshot of your flag logic in the generated client at build time. The SDK will instantly initialize from the snapshot first before fetching the latest flag logic from Hypertune Edge.
Add the following environment variable to your .env file:
Then regenerate the client.
You can keep the snapshot fresh by setting up a webhook to regenerate the client on every Hypertune commit. In this case, you don't need to initialize from Hypertune Edge at all, eliminating network latency and bandwidth, improving both performance and efficiency.
Next steps
Now you can update the logic for exampleFlag from the Hypertune UI without updating your code or waiting for a new build, deployment, or service restart.
To add a new flag, create it in the Hypertune UI then regenerate the client.