Reproduce default build discovering work circuits - #4391
Open
ShiboSoftwareDev wants to merge 1 commit into
Open
Conversation
ShiboSoftwareDev
marked this pull request as ready for review
August 20, 2026 23:40
Contributor
|
This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Running
tsci buildwithout a file argument scans every default board pattern before considering the detected main entrypoint. A project withindex.circuit.tsxtherefore also builds temporary diagnostic circuits underwork/, expanding build time and producing unintended outputs.Reproduction
The focused unit reproduction creates a project containing:
index.circuit.tsx, the conventional main entrypointwork/diagnostic.circuit.tsx, an iterative diagnostic circuitWith no
includeBoardFilesconfiguration and no explicit file/directory argument,getBuildEntrypointscurrently returns both files and does not identify the main entrypoint.The reproduction changes no CLI implementation.
Expected behavior
A no-argument build should use the conventional/configured main entrypoint when one exists. Multi-board discovery remains available through
includeBoardFilesor an explicit directory argument.Verification
bun test tests/cli/build/build-default-entrypoint-discovery.test.tsbun run format:checkThe fix will be proposed as a separate PR stacked on this branch.