Zach Feldman bc70da1a22 fix(web): resolve Bun workspace-hoisted node_modules in build script (#495) ... ## Why The build script in `apps/fabro-web/scripts/build.ts` hardcoded two paths that assumed packages live in `apps/fabro-web/node_modules/`: - `./node_modules/.bin/tailwindcss` (the Tailwind CLI invocation) - `join(rootPath, "node_modules", "@pierre", "diffs", ...)` (the worker asset copy) This repo uses Bun workspaces (root `package.json` has `workspaces: ['apps/*', 'lib/packages/*']`), so `bun install` hoists all packages to the repo root. Any fresh contributor install broke `bun run dev` immediately with: ``` ENOENT: no such file or directory, posix_spawn './node_modules/.bin/tailwindcss' ``` followed by: ``` ENOENT: no such file or directory, lstat '.../apps/fabro-web/node_modules/@pierre/diffs/...' ``` ## What changed - `tailwindcss` is now resolved via `Bun.which("tailwindcss")`, which searches `PATH` and the workspace root `node_modules/.bin/`, with the old path as fallback. - `pierreWorkerDir` now resolves from a `workspaceRoot` derived via `new URL("../../..", import.meta.url)` (repo root), matching where Bun actually installs workspace dependencies. ## Verification `bun run dev` from `apps/fabro-web/` completes a full build successfully after a clean `bun install` from the repo root. --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Bryan Helmkamp <bryan@brynary.com>		2026-06-12 08:23:56 -04:00
..
build.test.ts	fix(web): raise timeout for build tests that run a real vite build (#310)	2026-05-18 12:52:18 -04:00
build.ts	fix(web): resolve Bun workspace-hoisted node_modules in build script (#495)	2026-06-12 08:23:56 -04:00