Figma Code Connect doesn't work.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- figma, html, typescript
- Domain
- developer-experience, tooling
Research direction
Start by tracing how figma connect publish discovers files from figma.config.json, then inspect the HTML template parser path that handles placeholders in Code Connect mappings. Reproduce the reported monorepo glob and conditional-expression error against the supplied mapping; done means confirming the cause and documenting or fixing discovery and parser behavior for this Vue/HTML setup.
Written by the indexing model from the issue text.
Description
Title: Code Connect (Vue/HTML, monorepo) — “No Code Connect files found” + template ParserError
CLI: figma -V → 1.3.5
OS: Windows 11 Home Single Language — 10.0.26100 (Build 26100)
Project: Vue 3 (HTML parser), monorepo (packages/**/src/**)
Config (repo root figma.config.json):
{
"codeConnect": {
"parser": "html",
"include": ["packages/**/src/**/*.figma.ts"],
"exclude": ["**/dist/**", "**/node_modules/**"],
"label": "Vue 3"
}
}
Mapping file path:
packages/components/src/figma/default-button.figma.ts
Figma node URL (main component):
https://www.figma.com/design/E1fhIWXU1sQRP4ZItKgQu4/GDS-v3.16.1-----Zeta-Hacks-?node-id=27-5765
Mapping (minimal repro):
import figma, { html, text } from '@figma/code-connect/html';
figma.connect("https://www.figma.com/design/E1fhIWXU1sQRP4ZItKgQu4/GDS-v3.16.1-----Zeta-Hacks-?node-id=27-5765", {
props: {
text: figma.string("Text"),
leftIconInstance: figma.instance("Left Icon instance"),
rightIconInstance: figma.instance("Right Icon instance"),
iconOnlyInstance: figma.instance("Icon only instance"),
},
example: (p) => html`<gds-button>${text(p.text)}</gds-button>`,
imports: ["import { GdsButton } from '@your-scope/button'"]
});
Steps (CMD):
cd "C:\Users\mayan\OneDrive\Desktop\Figma Code\galaxy-design-system-main"set FIGMA_ACCESS_TOKEN=figd_xxxxxxxxxxxxxxxxxnpx figma connect publish
(Also tried:npx figma connect create "<node-url>"then publish.)
Actual result:
- Often: “No Code Connect files found …” (even with file present & glob above).
- When using conditionals inside
html\...`: **ParserError** — *Expected a call expression as a placeholder in the template, got ConditionalExpression*. Replaced withtext(...)` calls to avoid conditionals.
Questions:
- Are
?:/&&conditionals unsupported inside${ ... }for HTML templates? - For HTML/Vue projects, should we avoid the interactive wizard and use only
create/manual files? - Is my monorepo
includeglob correct, or is there a better recommended pattern?
Thanks!
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 126
- PR merge metrics
- No merged PRs in 30d
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 figma/code-connect
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
figma/code-connect#403 ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 38/100
figma/code-connect#414 ·
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
figma/code-connect#413 · 1 comment ·
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 54/100
figma/code-connect#412 · 1 comment ·
All issues in figma/code-connect
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
A live recovery copy treats a large whole number and text with the same digits as the same valueOpenbug sharing & sync
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
[prefer-expect-resolves] autofix leaves a stray ")" when the awaited expression is parenthesizedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jest-community/eslint-plugin-jest#2052 ·