Interactive setup runs with no output

[evwilkin]

Please provide:

• Code Connect CLI version 1.2.4
• Operating system MacOS Sequoia 15.1.1
• Code Connect file, Figma design and/or relevant code snippet that could help us get more context
  • Figma components file
  • figma.config.json setup & draft PR

We have a monorepo with several packages, but after running npx figma connect from both the root of the project as well as the root of the package containing the components (packages/react-core) we provide all the requested information, wait a minute while the command executes, and then it completes but no mappings are found or files created. Using npx figma create connect ... in each individual component directly to link it directly to a component/component set in the Figma file does work so we have been using that, but would prefer to take advantage of the automation if possible.

[karlpetersson]

Hey @evwilkin just to clarify, is the command you're trying to run npx figma connect (and not npx figma create)? E.g are you able to go through the wizard flow for connecting components, but no files are created?

[evwilkin]

Yes sorry about the typo! Correcting the original description now to reflect this

[slees-figma]

Hey @evwilkin! Thanks for the report. Please could you share either a screenshot or copy/paste the last bit of output of the CLI with the interactive setup? I cloned your repo and was able to complete the setup from packages/react-core, so would be helpful to know exactly which step is the problem. A couple more things to try:

• You can pass --verbose to see more detailed errors - though not sure this'll surface anything new
• We fixed a very similar bug a couple weeks ago in the last release (v1.2.4). It looks like you're on this anyway but worth triple checking as it sounds very similar!

[evwilkin]

Thanks for taking a look @slees-figma - here are two screenshots, the first run from the /react-core directory and the second from the same dir but passing ./src/components as the components directory, both with the same effect (I did confirm the v1.2.4 version seen in the first screenshot)

---

---

[evwilkin]

Also with the --verbose flag - I will note that initial run with this command without specifying the ./src/components directory did give a warning about a file in src/demos/... (Parsing local files...Could not parse exports of file...):

---

[slees-figma]

Thanks @evwilkin. Looking at the code there is an error being thrown in parsing the response of the Figma file but I can't tell what it would be. I've asked for file access via your support ticket so I can investigate further.