mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
A version written into a manifest is written into every manifest that wants it, which is how eslint came to exist in a hundred and four forms across this estate and how a package came to resolve twice at run time. The catalog moves the number out of the manifest: a manifest names the package, the workspace names the version. Four are held below their latest because the newer release cannot be used, and the reason is recorded rather than the version alone: @noble/hashes 2 renamed every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels 3 points its types condition at the bundle.
Insights Nuxt module
- Handles sourcemap configuration and upload for the Insights Error Tracking product
- Provides insights client and auto exception capture for Vue and Nitro
Please see the main Insights Error tracking docs.
Usage
- Install the package
pnpm add @hanzo/nuxt
- Configure insights module
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@hanzo/nuxt'], // Add module reference
sourcemap: { client: 'hidden' }, // Make sure to set it (otherwise client sourcemaps will not be generated)
nitro: {
rollupConfig: {
output: {
sourcemapExcludeSources: false, // Make sure to set it (otherwise server sourcemaps will not be generated)
},
},
},
insightsConfig: {
host: 'http://localhost:8010', // (optional) Host URL, defaults to https://us.insights.hanzo.ai
publicKey: 'public api key', // Your public web snippet key. You can find it in settings
clientConfig?: Partial<InsightsConfig> // (optional) It will be passed to the @hanzo/insights client on init in vue
serverConfig?: InsightsOptions // (optional) It will be passed to the @hanzo/insights-node client on init in nitro. Please note that this client instance is intended for error-tracking purposes only
sourcemaps: {
enabled: true, // Enables sourcemaps generation and upload
projectId: '2', // Project ID, see https://app.insights.hanzo.ai/settings/project#variables
releaseName: 'my-application', // (optional) Release name, defaults to git repository name
releaseVersion: '1.0.0', // (optional) Release version, defaults to current git commit
personalApiKey: 'personal api key', // Your personal API key. You can generate it in settings -> Personal API keys
},
},
})
- You can access your vue insights client inside vue using
// some-file.vue
const { $insights } = useNuxtApp()
Composables
The module provides auto-imported composables for working with feature flags:
useInsights()
Returns the Insights client instance.
<script setup>
const insights = useInsights()
insights.capture('event_name')
</script>
useFeatureFlagEnabled(flag: string)
Returns a reactive ref that checks if a feature flag is enabled (returns true/false/undefined).
<script setup>
const isEnabled = useFeatureFlagEnabled('my-flag')
</script>
<template>
<div v-if="isEnabled">Feature is enabled!</div>
</template>
useFeatureFlagVariantKey(flag: string)
Returns a reactive ref containing the feature flag value/variant (returns the variant string, true/false, or undefined).
<script setup>
const variant = useFeatureFlagVariantKey('my-flag')
</script>
<template>
<div v-if="variant === 'variant-a'">Show variant A</div>
<div v-else-if="variant === 'variant-b'">Show variant B</div>
</template>
useFeatureFlagPayload(flag: string)
Returns a reactive ref containing the feature flag payload (returns any JSON value or undefined).
<script setup>
const payload = useFeatureFlagPayload('config-flag')
</script>
<template>
<div v-if="payload">Config value: {{ payload.value }}</div>
</template>
All these composables automatically update when feature flags are loaded or changed.
- On the server side, the Insights client instance initialized by the plugin is intended exclusively for error tracking. If you require additional Insights client functionality for other purposes, please instantiate a separate client within your application as needed.
FAQ
Q: I see typescript errors in the insights config after adding this module
A: It is possible that after adding a new module to `modules` typescript will complain about types. Solution is to remove `.nuxt` directory and regenerate it by running `build` command you are using. This will properly regenerate config types.
Q: I see stack traces but I do not see line context in the error tracking tab
A: Double check whether you enabled sourcemaps generation in the nuxt config both for vue and nitro. It is covered in the docs.
Contributing
See CONTRIBUTING.md for package-specific development instructions.