Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

120 lines
4.4 KiB
TypeScript

import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
import { getNuxtSteps as getNuxtStepsPA } from '../product-analytics/nuxt'
import { StepDefinition } from '../steps'
export const getNuxt36Steps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
const { CodeBlock, Markdown, dedent } = ctx
const installSteps = getNuxtStepsPA(ctx)
const manualCaptureStep: StepDefinition = {
title: 'Manually capturing exceptions',
badge: 'optional',
content: (
<>
<Markdown>
{dedent`
To send errors directly using the Insights client, import it and use the \`captureException\` method like this:
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'html',
file: 'Vue',
code: dedent`
<script>
const { $insights } = useNuxtApp()
if ($insights) {
const insights = $insights()
insights.captureException(new Error("Important error message"))
}
</script>
`,
},
]}
/>
<Markdown>
{dedent`
On the server side, you can use the \`insights\` object directly.
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'javascript',
file: 'server/api/example.js',
code: dedent`
const runtimeConfig = useRuntimeConfig()
const insights = new Insights(
runtimeConfig.public.insightsPublicKey,
{
host: runtimeConfig.public.insightsHost,
}
);
try {
const results = await DB.query.users.findMany()
return results
} catch (error) {
insights.captureException(error)
}
`,
},
]}
/>
</>
),
}
const exceptionAutocaptureStep: StepDefinition = {
title: 'Configuring exception autocapture',
badge: 'recommended',
content: (
<>
<Markdown>
{dedent`
Update your \`insights.client.js\` to add an error hook.
`}
</Markdown>
<CodeBlock
blocks={[
{
language: 'javascript',
file: 'JavaScript',
code: dedent`
export default defineNuxtPlugin((nuxtApp) => {
...
nuxtApp.hook('vue:error', (error) => {
insightsClient.captureException(error)
})
...
})
`,
},
]}
/>
</>
),
}
const verifyStep: StepDefinition = {
title: 'Verify error tracking',
badge: 'recommended',
checkpoint: true,
content: (
<Markdown>
{dedent`
Before proceeding, let's make sure exception events are being captured and sent to Insights. You should see events appear in the activity feed.
[Check for exceptions in Insights](https://app.hanzo.ai/activity/explore)
`}
</Markdown>
),
}
return [...installSteps, manualCaptureStep, exceptionAutocaptureStep, verifyStep]
}
export const Nuxt36Installation = createInstallation(getNuxt36Steps)