Hypertune
  • Introduction
  • Getting Started
    • Set up Hypertune
    • Next.js (App Router) quickstart
    • Next.js (Pages Router) quickstart
    • React quickstart
    • Remix quickstart
    • Gatsby quickstart
    • Vue quickstart
    • Nuxt quickstart
    • Node.js quickstart
    • React Native quickstart
    • JavaScript quickstart
    • Python quickstart
    • Rust quickstart
    • Go quickstart
    • Web quickstart
    • GraphQL quickstart
  • Example apps
    • Next.js and Vercel example app
  • Concepts
    • Architecture
    • Project
    • Schema
    • Flag lifecycle
    • Logic
    • Variables
    • Splits
    • A/B tests
    • Staged rollouts
    • Multivariate tests
    • Machine learning loops
    • Events
    • Funnels
    • Hypertune Edge
    • Reduction
    • SDKs
    • GraphQL API
    • Git-style version control
    • App configuration
  • Use Cases
    • Feature flags and A/B testing
    • Landing page optimization
    • In-app content management
    • Pricing plan management
    • Permissions, rules and limits
    • Optimizing magic numbers
    • Backend configuration
    • Product analytics
  • Integrations
    • Vercel Edge Config integration
    • Google Analytics integration
    • Segment integration
    • Webhooks
      • Creating webhooks
      • Handling webhooks
  • SDK Reference
    • Installation
    • Type-safe client generation
    • Initialization
    • Build-time logic snapshot
    • Hard-coded fallbacks
    • Local-only, offline mode
    • Hydrate from your own server
    • Wait for server initialization
    • Provide targeting attributes
    • Local, synchronous evaluation
    • Remote logging
    • Getting flag updates
    • Serverless environments
    • Vercel Edge Config
    • Custom logging
    • Shutting down
Powered by GitBook
On this page
  • 1. Install hypertune
  • 2. Set environment variables
  • 3. Generate the client
  • 4. Use the client
  • 5. (Optional) Include a build-time logic snapshot
  • That's it
  1. Getting Started

Vue quickstart

1. Install hypertune

Once you have a Vue application ready, install Hypertune's JavaScript SDK:

npm install hypertune
yarn add hypertune
pnpm add hypertune

2. Set environment variables

Define the following environment variables in your .env file:

VITE_HYPERTUNE_TOKEN=token
HYPERTUNE_FRAMEWORK=vue
HYPERTUNE_OUTPUT_DIRECTORY_PATH=src/generated

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:

npx hypertune
yarn hypertune
pnpm hypertune

4. Use the client

Add the generated hypertunePlugin to your app:

src/main.ts
import { createApp } from "vue";
import { hypertunePlugin } from "./generated/hypertune.vue";
import App from "./App.vue";
import "./style.css";

createApp(App)
  .use(hypertunePlugin, {
    createSourceOptions: {
      token: import.meta.env.VITE_HYPERTUNE_TOKEN!,
    },
    rootArgs: {
      context: {
        environment: "development",
        user: { id: "1", name: "Test", email: "hi@test.com" },
      },
    },
  })
  .mount("#app");

Then use the generated useHypertune composable to access your flags:

src/components/Example.vue
<script setup lang="ts">
import { useHypertune } from "../generated/hypertune.vue";

const hypertune = useHypertune();
</script>

<template>
  <div>
    Example Flag: {{ hypertune.exampleFlag({ fallback: false }) }}
  </div>
</template>

If you have a Content Security Policy, add the following URLs to the connect-src directive: https://edge.hypertune.com https://gcp.fasthorse.workers.dev

This lets the browser send analytics back to Hypertune so you can see how often different parts of your flag logic are evaluated, e.g. to see how many sessions fall into each targeting rule, as well as analytics for your events, A/B tests and machine learning loops.

5. (Optional) Include a build-time logic snapshot

To avoid this, 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:

HYPERTUNE_INCLUDE_INIT_DATA=true

Then regenerate the client.

That's it

Now you can update the logic for exampleFlag from the Hypertune UI without updating your code or waiting for a new build, deployment or app release.

To add a new flag, create it in the Hypertune UI then regenerate the client.

PreviousGatsby quickstartNextNuxt quickstart

Last updated 8 months ago

If you try accessing a flag on the first app render, you'll get your hardcoded fallback value if the SDK hasn't initialized from yet. This can result in a UI flicker or layout shift if the flag value changes when the SDK initializes.

You can keep the snapshot fresh by setting up a to regenerate the client and redeploy your app on every Hypertune commit. In this case, you don't need to initialize from Hypertune Edge at all.

Hypertune Edge
webhook