Files
web/vitest.config.ts
zeekay b0eccb2156 chore: resolve @zap-proto/zap from npm (^1.1.0)
@zap-proto/zap is published to npm at 1.1.0 (native ZAP wire runtime).
Drop the local-dev scaffolding that bridged the pre-publish gap:

- dep: @zap-proto/zap ^0.1.0 -> ^1.1.0
- remove pnpm.overrides -> link:../ts (the link workaround is obsolete)
- remove the vitest alias to ../ts/src; tests now resolve @zap-proto/zap
  via plain npm semver — the runtime under test is exactly what ships.

All imported symbols (buildRequest/buildResponse/parseRequest/parseResponse,
NO_TARGET, Status, Call, Response, ZapParseError) exist in the 1.1.0
surface. pnpm install && test && build && typecheck all pass against the
npm-resolved dependency.
2026-06-15 19:41:14 -07:00

11 lines
306 B
TypeScript

import { defineConfig } from "vitest/config";
// @zap-proto/zap is resolved from npm (^1.1.0). The runtime under test is
// exactly what ships to consumers — no source alias, no link override.
export default defineConfig({
test: {
include: ["test/**/*.test.ts"],
environment: "node",
},
});