Vue

schematic-vue is a client-side Vue library for Schematic which provides composables to track events, check flags, and more. schematic-vue provides the same capabilities as schematic-js, for Vue apps.

Install

$
npm install @schematichq/schematic-vue
$
# or
$
yarn add @schematichq/schematic-vue
$
# or
$
pnpm add @schematichq/schematic-vue

Usage

SchematicPlugin

You can use the SchematicPlugin to make Schematic available throughout your Vue application:

1
import { createApp } from "vue";
2
import { SchematicPlugin } from "@schematichq/schematic-vue";
3
import App from "./App.vue";
4
5
const app = createApp(App);
6
app.use(SchematicPlugin, { publishableKey: "your-publishable-key" });
7
app.mount("#app");

Setting context

To set the user context for events and flag checks, you can use the identify function provided by the useSchematicEvents composable:

1
<script setup lang="ts">
2
import { onMounted } from "vue";
3
import { useSchematicEvents } from "@schematichq/schematic-vue";
4
5
const { identify } = useSchematicEvents();
6
7
onMounted(() => {
8
  identify({
9
    keys: { id: "my-user-id" },
10
    company: {
11
      keys: { id: "my-company-id" },
12
      traits: { location: "Atlanta, GA" },
13
    },
14
  });
15
});
16
</script>

To learn more about identifying companies with the keys map, see key management in Schematic public docs.

Tracking usage

Once you’ve set the context with identify, you can track events:

1
<script setup lang="ts">
2
import { useSchematicEvents } from "@schematichq/schematic-vue";
3
4
const { track } = useSchematicEvents();
5
6
function handleQuery() {
7
  track({ event: "query" });
8
}
9
</script>
10
11
<template>
12
  <button @click="handleQuery">Run Query</button>
13
</template>

If you want to record large numbers of the same event at once, or perhaps measure usage in terms of a unit like tokens or memory, you can optionally specify a quantity for your event:

1
track({ event: "query", quantity: 10 });

Checking flags

To check a flag, you can use the useSchematicFlag composable:

1
<script setup lang="ts">
2
import { useSchematicFlag } from "@schematichq/schematic-vue";
3
4
const isFeatureEnabled = useSchematicFlag("my-flag-key");
5
</script>
6
7
<template>
8
  <div v-if="isFeatureEnabled">
9
    <Feature />
10
  </div>
11
  <div v-else>
12
    <Fallback />
13
  </div>
14
</template>

Checking entitlements

You can check entitlements (i.e., company access to a feature) using a flag check as well, and using the useSchematicEntitlement composable you can get additional data to render various feature states:

1
<script setup lang="ts">
2
import {
3
  useSchematicEntitlement,
4
  useSchematicIsPending,
5
} from "@schematichq/schematic-vue";
6
7
const schematicIsPending = useSchematicIsPending();
8
const {
9
  featureAllocation,
10
  featureUsage,
11
  featureUsageExceeded,
12
  value: isFeatureEnabled,
13
} = useSchematicEntitlement("my-flag-key");
14
</script>
15
16
<template>
17
  <!-- Loading state -->
18
  <Loader v-if="schematicIsPending" />
19
20
  <!-- Usage exceeded state -->
21
  <div v-else-if="featureUsageExceeded">
22
    You have used all of your usage ({{ featureUsage }} / {{ featureAllocation }})
23
  </div>
24
25
  <!-- Either feature state or "no access" state -->
26
  <Feature v-else-if="isFeatureEnabled" />
27
  <NoAccess v-else />
28
</template>

Note: useSchematicIsPending is checking if entitlement data has been loaded, typically via identify. It should, therefore, be used to wrap flag and entitlement checks, but never the initial call to identify.

Fallback Behavior

The SDK includes built-in fallback behavior you can use to ensure your application continues to function even when unable to reach Schematic (e.g., during service disruptions or network issues).

Flag Check Fallbacks

When flag checks cannot reach Schematic, they use fallback values in the following priority order:

1. Callsite fallback - fallback values can be provided directly in the composable options
2. Initialization defaults - fallback values configured via flagCheckDefaults or flagValueDefaults options when initializing the plugin
3. Default value - Returns false if no fallback is configured

1
<script setup lang="ts">
2
// Provide a fallback value at the callsite
3
import { useSchematicFlag } from "@schematichq/schematic-vue";
4
5
const isFeatureEnabled = useSchematicFlag("feature-flag", {
6
    fallback: true,  // Used if API request fails
7
});
8
</script>
9
10
<template>
11
    <Feature v-if="isFeatureEnabled" />
12
    <Fallback v-else />
13
</template>

1
// Or configure defaults at initialization
2
import { createApp } from "vue";
3
import { SchematicPlugin } from "@schematichq/schematic-vue";
4
5
const app = createApp(App);
6
app.use(SchematicPlugin, {
7
    publishableKey: "your-publishable-key",
8
    flagValueDefaults: {
9
        "feature-flag": true,  // Used if API request fails and no callsite fallback
10
    },
11
    flagCheckDefaults: {
12
        "another-flag": {
13
            flag: "another-flag",
14
            value: true,
15
            reason: "Default value",
16
        },
17
    },
18
});

Event Queueing and Retry

When events (track, identify) cannot be sent due to network issues, they are automatically queued and retried:

• Events are queued in memory (up to 100 events by default, configurable via maxEventQueueSize)
• Failed events are retried with exponential backoff (up to 5 attempts by default, configurable via maxEventRetries)
• Events are automatically flushed when the network connection is restored
• Events queued when the page is hidden are sent when the page becomes visible

WebSocket Fallback

In WebSocket mode, if the WebSocket connection fails, the SDK will provide the last known value or the configured fallback values as outlined above. The WebSocket will also automatically attempt to re-establish it’s connection with Schematic using an exponential backoff.

Options API Support

While the primary API uses the Composition API, you can still use these composables in the Options API:

1
<script>
2
import { useSchematicFlag, useSchematicEvents } from "@schematichq/schematic-vue";
3
4
export default {
5
  setup() {
6
    const isFeatureEnabled = useSchematicFlag("my-flag-key");
7
    const { track } = useSchematicEvents();
8
9
    return {
10
      isFeatureEnabled,
11
      track,
12
    };
13
  },
14
  methods: {
15
    handleAction() {
16
      this.track({ event: "action" });
17
    },
18
  },
19
};
20
</script>

Troubleshooting

For debugging and development, Schematic supports two special modes:

Debug Mode

Enables console logging of all Schematic operations:

1
// Enable at initialization
2
import { createApp } from "vue";
3
import { SchematicPlugin } from "@schematichq/schematic-vue";
4
5
const app = createApp(App);
6
app.use(SchematicPlugin, {
7
  publishableKey: "your-publishable-key",
8
  debug: true,
9
});
10
11
// Or via URL parameter
12
// https://yoursite.com/?schematic_debug=true

Offline Mode

Prevents network requests and returns fallback values for all flag checks:

1
// Enable at initialization
2
import { createApp } from "vue";
3
import { SchematicPlugin } from "@schematichq/schematic-vue";
4
5
const app = createApp(App);
6
app.use(SchematicPlugin, {
7
  publishableKey: "your-publishable-key",
8
  offline: true,
9
});
10
11
// Or via URL parameter
12
// https://yoursite.com/?schematic_offline=true

Offline mode automatically enables debug mode to help with troubleshooting.

Advanced Usage

Using a Pre-configured Client

If you need more control over the Schematic client initialization, you can create a client instance and pass it to the plugin:

1
import { createApp } from "vue";
2
import { Schematic } from "@schematichq/schematic-js";
3
import { SchematicPlugin } from "@schematichq/schematic-vue";
4
import App from "./App.vue";
5
6
const client = new Schematic("your-publishable-key", {
7
  useWebSocket: true,
8
  debug: true,
9
});
10
11
const app = createApp(App);
12
app.use(SchematicPlugin, { client });
13
app.mount("#app");

Per-Component Client Override

You can override the client for a specific component by passing a client option to any composable:

1
import { useSchematicFlag } from "@schematichq/schematic-vue";
2
import { Schematic } from "@schematichq/schematic-js";
3
4
const customClient = new Schematic("different-api-key");
5
const isFeatureEnabled = useSchematicFlag("my-flag-key", {
6
  client: customClient,
7
});

Server-Side Rendering (SSR)

All composables are SSR-compatible and work seamlessly with Nuxt and other Vue SSR frameworks:

• Initial flag/entitlement values are retrieved synchronously for server-side rendering
• Real-time subscriptions are deferred to client-side hydration
• No special configuration needed - it just works!

1
// plugins/schematic.ts
2
import { SchematicPlugin } from '@schematichq/schematic-vue'
3
4
export default defineNuxtPlugin((nuxtApp) => {
5
  const config = useRuntimeConfig()
6
  nuxtApp.vueApp.use(SchematicPlugin, { publishableKey: config.public.schematicPublishableKey })
7
})

1
<!-- Works in Nuxt/SSR -->
2
<script setup lang="ts">
3
import { useSchematicFlag } from "@schematichq/schematic-vue";
4
5
// Initial value available on server, updates subscribed on client
6
const isFeatureEnabled = useSchematicFlag("my-feature");
7
</script>

License

MIT

Support

Need help? Please open a GitHub issue or reach out to support@schematichq.com and we’ll be happy to assist.