Environment
- macOS
- Node v24.14.0
- npm v11.9.0
- @figma/code-connect running via npx
- Company managed Mac
Issue
Running:
npx figma connect create "" -t
Results in:
Fetching component information from Figma...
Failed to create: TypeError: fetch failed
What I verified
✅ npx figma connect --help works
✅ Token works:
curl -H "X-Figma-Token: " https://api.figma.com/v1/me
✅ File API works:
curl ... /v1/files/
✅ Node API works:
curl ... /v1/files//nodes?ids=
✅ Component URL is valid
✅ Tested both:
- SDS sample file
- Newly created test file with a simple component
✅ Tried with VPN connected and disconnected
Observed behaviour
Code Connect reaches:
Fetching component information from Figma...
and then fails with:
Question
Are there any known issues with:
- Node 24.x
- macOS managed devices
- Code Connect metadata fetch endpoint
that could cause this behaviour even though standard Figma API calls succeed?
`
Environment
Issue
Running:
npx figma connect create "" -t
Results in:
Fetching component information from Figma...
Failed to create: TypeError: fetch failed
What I verified
✅ npx figma connect --help works
✅ Token works:
curl -H "X-Figma-Token: " https://api.figma.com/v1/me
✅ File API works:
curl ... /v1/files/
✅ Node API works:
curl ... /v1/files//nodes?ids=
✅ Component URL is valid
✅ Tested both:
✅ Tried with VPN connected and disconnected
Observed behaviour
Code Connect reaches:
Fetching component information from Figma...
and then fails with:
Question
Are there any known issues with:
that could cause this behaviour even though standard Figma API calls succeed?
`