fix: cache the SDK dist/ output in turbo - #8
Conversation
|
@pyjeebz is attempting to deploy a commit to the Goshen Labs Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Turborepo build task configuration so Turbo recognizes and caches the SDK’s dist/ build artifacts, eliminating the “no output files found” warning and enabling cache hits for subsequent SDK builds.
Changes:
- Add
dist/**to thebuildtaskoutputsinturbo.jsonso Turbo captures SDK build output for caching.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Greptile SummaryThis PR updates Turbo's shared build cache outputs for the SDK package. The main change is:
Confidence Score: 5/5Safe to merge with minimal risk. The change is a single Turbo configuration update that matches the described SDK build output and does not alter runtime behavior. No files require special attention.
What T-Rex did
Important Files Changed
Reviews (1): Last reviewed commit: "fix: cache the SDK dist/ output in turbo" | Re-trigger Greptile |
Every
npm run build/npm run checkcurrently prints:The SDK compiles into
dist/, but the sharedbuildtask'soutputsonly lists.svelte-kit/**,build/**, and.vercel/**, so turbo never captures (or caches) the SDK build.This adds
dist/**to the list. Verified locally: the warning is gone, and a repeatturbo build --filter=boring-computers-sdkgoes from ~16s to a full cache hit (~70ms).🤖 Generated with Claude Code