From 80f94d9663934fb8601e783f7cfbdfd86bba7a4c Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Tue, 14 Jul 2026 08:14:16 +0000 Subject: [PATCH] docs(agents): clarify sibling data0/src resolution in combined workspace Co-authored-by: Zhenyu Hou --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 7080432..0ba9e1f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -12,7 +12,7 @@ Services / commands (see `package.json` scripts): Gotchas: - Browser tests need the Playwright chromium browser **and** its system libraries. The update script runs `npx playwright install chromium`, but the OS libraries (`--with-deps`, needs sudo) are part of the base image, not the update script. - There is no lint script. `npx tsc --noEmit -p tsconfig.json` reports **pre-existing** errors in `__tests__/*.typespec.tsx` and a few spec files; it is not wired into `build` (which uses `vite-plugin-dts`) or CI. Rely on `npm run build` + `npx vitest run` as the quality gates. -- `data0` (the reactive core) resolves from the npm-installed package unless a sibling `../data0/src` checkout exists (see `vite.config.ts`); no sibling checkout is present here. +- `data0` (the reactive core) resolves from the npm-installed package unless a sibling `../data0/src` checkout exists (the alias is applied in `vitest.config.ts`; it is commented out in `vite.config.ts`). When `axii`, `data0`, and `axle` are checked out side by side (as in the combined `axiijs` workspace), `npx vitest run` runs against `../data0/src` directly, so edits to `data0` source are picked up live without rebuilding/reinstalling. ## Performance is a core goal