an interesting thing that im seeing is
an interesting thing that im seeing is that with a capacitor, it works when i rotate it by 90 degrees (counterclockwise) but not with -90.


13 Replies
Yea that is very weird, btw we updated schematic symbols, might work on refresh, i will verify now
oh that's expected behavior actually, since your GND is up it's not being replaced w/ a symbol
@i use arch btw. if you refresh you should have rail symbols now

if im running locally, what package do i need to update?
i think just
tscircuit
are you using a global install? Then npm install -g tscircuit
lmkim on bun
idk if i mess something up but i ran
bun update tscircuit
and restarted tsci dev, but it's still doing the same thing.
try
bun update --latest tscircuit
you can do npm ls schematic-symbols
for good measure, and note that it will require restart
(of the server)
lmk- i might add tsci upgrade
in the future because these issues are annoying
[email protected] or 0.0.201 i believe is the version you'll need@tsci/[email protected] /home/h3ck4r/Documents/capacitive_button
├─┬ @tscircuit/[email protected]
│ └── [email protected] deduped
├── [email protected]
└─┬ [email protected]
├─┬ @tscircuit/[email protected]
│ └── [email protected] deduped
└── [email protected]
i have two verisons rn
hmm, this is weird hold on
i'm confused, can you do
npm ls @tscircuit/runframe
as well, sorry@tsci/[email protected] /home/h3ck4r/Documents/capacitive_button
└─┬ [email protected]
└── @tscircuit/[email protected]
i'm also doing some dep updates to other projects just to make sure there are no version conflicts which could be related to the issue. I would generally recommend ONLY installing "tscircuit" in most packages, because overriding dependencies is more of an advanced case
hmm ok
npm ls @tscircuit/cli
, last one@tsci/[email protected] /home/h3ck4r/Documents/capacitive_button
└─┬ [email protected]
└── @tscircuit/[email protected]
ok yea this is on us, i think we have some weird dep stuff, i'm going to just do a couple patches and we should be good in 20 mins as things deploy. Sorry about that
ok so we've released an update,
bun update --latest tscircuit
with [email protected]
if npm ls @tscircuit/cli
return v0.1.213
then you should be in good shape. We've fixed 50% of the problem for the future, in general we need more automations around updating so sometimes tscircuit.com and the cli can get slightly mismatched