turbo boundaries: how to ignore output folders from turbo scanning for imports?

[Raanelom]

Summary

With the latest version of turbo (2.8.12, and also in canary), the turbo boundaries command also scans all my dist and output folders that are included in my .gitignore. I've read all the documentation there is about turbo boundaries, but couldn't find an option to exclude certain directories. On a clean (mono)repo it runs fine, but after a single build all my output files are scanned as well.

Additional information

No response

Example

No response

[manimovassagh]

turbo boundaries respects your .gitignore for source scanning, but it sounds like it might not be doing that correctly for you. A few things to check:

1. Make sure your output directories are in .gitignore at the repo root (not just a nested .gitignore). For example:

dist/
build/
.next/

2. Try adding a boundaries config to your turbo.json — you can use globalPassThroughDirs or adjust your task outputs declarations so turbo knows those folders are build artifacts.

3. As a workaround, you can also try running turbo boundaries from a clean checkout (or after git clean -fdx) to confirm it is indeed the dist folders causing the noise.

If your .gitignore already covers those paths and turbo is still scanning them, this is likely a bug. I would suggest opening a GitHub issue with your directory structure and .gitignore contents — the turbo team has been actively iterating on the boundaries feature and this seems like a gap they would want to fix.