Files
insights/common/storybook/.storybook/plugins/vite-frontend-resolve-plugin.ts
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

54 lines
2.4 KiB
TypeScript

import { isBuiltin } from 'node:module'
import * as path from 'path'
import type { Plugin } from 'vite'
// Storybook bundles source from several workspaces (the app, quill, the mcp ui-apps)
// but CI installs only @hanzo/storybook's dependency closure. So a bare dep can be
// absent from the importer's own node_modules yet present up an installed package's
// chain — e.g. `lucide-react` imported from services/mcp source (aliased in via
// `@hanzo/mcp-ui`, and services/mcp is not in the closure) is installed under
// `@hanzo/quill`, which the app depends on. The old webpack config papered over
// this with `resolve.modules: [frontend/node_modules, <root>/node_modules,
// 'node_modules']`; Vite/Rollup resolves relative to the importer only.
//
// This resolves bare specifiers from a set of installed "anchor" files (the app and
// quill) before the importer. Each anchor is a real file whose node_modules chain is
// guaranteed installed in CI. First hit wins; if none resolve (the dep lives only in
// the importer's own node_modules, as in a full local install), return null and let
// Vite's normal importer-relative resolution handle it.
//
// Source packages aliased to their checkout (e.g. `@hanzo/quill`, `@hanzo/mcp-ui`)
// never reach this plugin — Vite's alias plugin runs first.
export function frontendResolvePlugin(repoRoot: string): Plugin {
// Real files on disk — Vite's resolver falls back to the wrong root for a
// non-existent importer and silently resolves nothing.
const anchors = [
path.join(repoRoot, 'frontend', 'src', 'index.tsx'),
path.join(repoRoot, 'packages', 'quill', 'packages', 'quill', 'src', 'index.ts'),
]
return {
name: 'frontend-node-modules-resolve',
enforce: 'pre',
async resolveId(source, importer, options) {
if (
!source ||
source[0] === '.' ||
source[0] === '\0' ||
anchors.includes(importer as string) ||
path.isAbsolute(source) ||
isBuiltin(source)
) {
return null
}
for (const anchor of anchors) {
const resolved = await this.resolve(source, anchor, { ...options, skipSelf: true })
if (resolved) {
return resolved
}
}
return null
},
}
}