<connector standard="usb_c" /> default part fails its own cutout clearance check, so autorouting is skipped for the whole board
Maintainers usually reply within 1 day
@Shokun123 is already working on this.
Since Nov 3, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- devtools
Research direction
Reproduce with the TSX snippet via tsci build, which should report two placement errors on USBC.pin15 and USBC.pin26. Start from how <connector standard="usb_c" /> picks its default JLCPCB part (C2765186), and from the placement clearance check that runs before Board._runLocalAutorouting. Done means the default part passes the built-in checks, so the trace from USBC.CC1 to R1.pin1 gets routed without placementDrcChecksDisabled.
Written by the indexing model from the issue text.
Description
Summary
With no part pinned, <connector standard="usb_c" /> resolves to JLCPCB C2765186. That footprint's pads pin15 and pin26 sit 0.171mm from the footprint's own cutouts, below the 0.200mm placement rule. The two pcb_placement_errors make autorouting skip the entire board, so a board with the default USB-C connector ends up with no traces at all, even when the connector is placed with plenty of free space.
Reproduction
export default () => (
<board width="30mm" height="20mm">
<connector name="USBC" standard="usb_c" />
<resistor name="R1" resistance="5.1k" footprint="0402" pcbX={10} />
<trace from="USBC.CC1" to="R1.pin1" />
</board>
)
tsci build output:
Copper for USBC.pin15 violates clearance to cutout unnamed cutout (measured 0.171mm, required 0.200mm)
Copper for USBC.pin26 violates clearance to cutout unnamed cutout (measured 0.171mm, required 0.200mm)
Autorouting was skipped because 2 PCB placement errors were found. Fix the placement errors or set placementDrcChecksDisabled to true to route anyway.
Trace [USBC.CC1 to R1.pin1] is not connected (it has no PCB trace)
Resulting circuit JSON: 0 pcb_trace. The source component has supplier_part_numbers: { jlcpcb: ["C2765186", "C456012", "C393939"] }.
Expected
The default part for a built-in standard passes the built-in placement checks, so a board using <connector standard="usb_c" /> routes without extra configuration.
Workarounds confirmed
- Pin a different part:
supplierPartNumbers={{ jlcpcb: ["C165948"] }}reports no placement errors and routes (1 trace). placementDrcChecksDisabledon<board>lets routing run, at the cost of disabling all placement checks.
Possibly related
In tsci dev, a board with the default USB-C connector did not draw the connector, and the console repeatedly logged:
Async effect error in PcbTraceRender "autorouting":
TypeError: Cannot read properties of undefined (reading 'x')
at getSimpleRouteJsonFromCircuitJson
at Board._runLocalAutorouting
That was on a larger board, and I haven't reduced it to a minimal case.
Environment
- tscircuit 0.0.3062 (latest on npm at time of writing), @tscircuit/core 0.0.2259
- Bun 1.4.4, Node 26.9.0
- macOS 26.6.2 (Apple Silicon)
- Dominant language
- TypeScript
- Stars
- 61
- Forks
- 256
- Avg merge
- 20h 21m
- Merged PRs (30d)
- 289
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tscircuit/core
-
Standalone `import("@tscircuit/core")` fails with `ERR_MODULE_NOT_FOUND` due to `devDependencies`-only imports in `dist/`Possibly taken @Andresdev14 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
tscircuit/core#5508 · 1 comment ·
Maintainers usually reply within 1 day
-
Default solder paste aperture is 0.7x the pad (49% of its area)Possibly taken @zainrizvi0611-cmd claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
tscircuit/core#4800 · 1 comment ·
Maintainers usually reply within 1 day
-
SCHEMATIC_COMPONENT_OUTLINE_COLOR "rgba(132, 0, 0)" is not portable SVG color; strict SVG renderers reject schematic outputPossibly taken @zainrizvi0611-cmd claimed this 17 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Scientific notation is truncated in simulation graph scale and offset settingsPossibly taken @Crodify claimed this 9 days ago. Openno-issue-activity
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tscircuit/core#3732 · 1 comment ·
Maintainers usually reply within 1 day
-
SchematicRect drops fillColor from circuit JSON and renders filled rectangles with the stroke colorPossibly taken @cocvn157 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openclaw/openclaw#199885 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
feature needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
sequant-io/sequant#1689 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100