39 Replies
idk what people were doing where this wasn't exported
im not sure if my code is just broken, but i'm still getting the error. and i think im on latest
that should be the right version, one sec, let me see if i can repro
oh wait i think i might've messed up
wait nvm again i think its still broken
oh lol
it seems to work on the web version. but it doesn't work locally
yea i think it's just caching
yeah prob
although i think @Rishabh made it so local node_modules should be used in all cases 🤔
yeah
is it working now
kinda
the original problem is fixed now
but now
@Abse did you test the XiaoReceiver?
sorry @itsme there must be a board being used in the XiaoReceiver
import { XiaoBoard } from "./XiaoBoard.circuit"
import type { ChipProps } from "@tscircuit/props"
export const XiaoReceiver = (props: ChipProps & { children?: any }) => {
return <XiaoBoard variant="Receiver" {...props} />
}
i think xiaoreceiver is just xiaoboard with a variant
this is so stupid
and xiaoboard has a board in it
Yeah
It should only be a group?
It should be a chip, he's trying to place a xiao component
Ok
I can fix it in 15 min I'm afk sorry for this
i'm fixing it now
GitHub
Refine XiaoReceiver by seveibar · Pull Request #54 · tscircuit/co...
Summary
mark XiaoReceiver pin labels as a const map for stronger literal inference
type XiaoReceiver props with ChipProps so connections are validated
Testing
bunx tsc --noEmit
bun run format
...
@itsme we'll need for the cdns to update but should be readyish soon
@itsme hopefully this is working better now, lmk if you run into any issues, we merged like 4 PRs related to this but I think some of the stuff is still not upstream... the kicad component pin numbers I think @Techmannih might help us get upstream
https://github.com/tscircuit/common/pull/55 not a big issue but i just added silkscreen outlines for the XiaoReceiver
yea we can merge if you update the snapshot with
tsci snapshot --updatedone
how long should i expect to wait to see changes? the silkscreen pr still doesn't seem to be there.
assuming you've updated locally and the issue is the CDN, generally 30 minutes is about how long it takes
it should be live now
maybe try a hard refresh of your page with cmd+shift+r
i tried a hard refresh and incognito mode doesnt seem to be working either
hmm
jsdelivr is reporting 0.0.27 is being served https://www.jsdelivr.com/package/npm/@tscircuit/common?tab=files
Did you do
bun update --latest @tscircuit/commonjsDelivr
@tscircuit/common CDN by jsDelivr - A CDN for npm and GitHub
A free, fast, and reliable CDN for @tscircuit/common. These are community-contributed "common" boards or components distributed with tscircuit
yeah
let me see if ican see it
Heinrich-XIAO/tsci-split-kbd - tscircuit
This code defines a PCB layout with a 3x5 grid of keys and diodes connected along row and column lines, featuring a XiaoReceiver component interfaced via traced pin connections. For the package "@tsci/Heinrich-XIAO.tsci-split-kbd":
Import:
Usage:
```tsx
export default () => (...
yea i reproduced
it's the CDN https://cdn.jsdelivr.net/npm/@tscircuit/common/+esm
it's returning 0.0.25
can you do this for now
there will be a better fix in the future, @Rishabh worked on local node modules loading but i guess it's not working
it works now.
sry about that- we will get local module loading working (CC @AyushJ or @Mustafa7 something to get into, probably requires seeing why the CLI isn't uploading these to the file server)