Files
zeekay 8a4a6bfe6d make build lands every target in dist/
make build builds the workspace, or one target with target=chrome
(firefox, safari, or any packages/<name>). browser writes dist/chrome,
firefox and safari itself; every other package builds in place, where
its package.json points, and dist/<name> links to it. make test runs
every suite, and all of them pass.

The Makefile, README and root src/, scripts/, test/, docs/, examples/,
benchmark/ and tsconfigs belonged to the hanzo-dev CLI this repo used
to be; none of it built or described anything here. CLAUDE.md, AGENTS.md
and GEMINI.md are symlinks to LLM.md and stay out of git.

jupyter ran a jupyter binary nobody installs; it runs under uvx pinned
to jupyterlab 4.5, since 4.6 fetches core metadata from GitHub at build
time. pdf's tests load pdf.js's legacy build, the one made for Node.
vscode's test is its vitest suite; the Electron harness is test:electron.

Claude-Session: https://claude.ai/code/session_01Dc8DXc3fEQCRHUa6XWK4Ku
2026-09-29 11:45:42 -07:00

14 lines
395 B
TypeScript

import { defineConfig } from 'vitest/config';
export default defineConfig({
// The modern pdf.js build calls Uint8Array.prototype.toHex, which browsers
// have and Node 24 does not; the legacy build is pdf.js's build for Node.
resolve: {
alias: { 'pdfjs-dist': 'pdfjs-dist/legacy/build/pdf.mjs' },
},
test: {
include: ['tests/**/*.test.ts'],
environment: 'node',
},
});