`thickness` on one `<trace>` widens every autorouted trace on the same net
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- tooling
Research direction
The issue gives a full repro but no file: start where <trace> props are parsed into trace records, then follow how the autorouter derives width and name for each connection on a net. Compare against the existing <net nominalTraceWidth> handling, which is the intended per-net path, and check why a per-trace thickness leaks into the net-level default and into sibling traces' labels. Done means the repro compiles to Circuit JSON where only the R1.pin2–R2.pin1 pcb_trace is 0.8mm and each trace keeps its own name.
Written by the indexing model from the issue text.
Description
Setting thickness on one <trace> makes every autorouted trace on that net use that width, including traces that didn't ask for it.
export default () => (
<board width="30mm" height="20mm">
<resistor name="R1" resistance="1k" footprint="0603" pcbX={-10} pcbY={5} />
<resistor name="R2" resistance="1k" footprint="0603" pcbX={10} pcbY={5} />
<resistor name="R3" resistance="1k" footprint="0603" pcbX={-10} pcbY={-5} />
<resistor name="R4" resistance="1k" footprint="0603" pcbX={10} pcbY={-5} />
{/* only this trace asks for 0.8mm */}
<trace from="R1.pin2" to="R2.pin1" thickness="0.8mm" />
{/* same net, no thickness */}
<trace from="R3.pin2" to="net.VBUS" />
<trace from="R4.pin1" to="net.VBUS" />
<trace from="R1.pin2" to="net.VBUS" />
</board>
)
Result: all three pcb_traces on the net are 0.8 mm wide, and all three are labelled R1.pin2 to R2.pin1, the thick trace's name, even the ones that run to R3 and R4.
Expected: only the R1–R2 connection is 0.8 mm; the others use the default width. <net nominalTraceWidth> already exists for the case where the whole net should be wide.
Why it matters:
- On a real board (a USB-C powered LED dimmer), I set
thickness="0.5mm"on two traces for the LED-strip current path. The whole V5 and LED_N nets went to 0.5 mm, including the hookups to small decoupling caps and 0402 resistors, which crowded the board and caused clearance errors. - Because every trace on the net takes the thick trace's name, DRC messages point at the wrong connection. For example, I got
PCB trace Q1.D to J1.LED_N is too close to U1.RESET to net.V5for copper that was actually on a different branch of the net.
Versions: tscircuit 0.0.3188, @tscircuit/core 0.0.2380
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day