Skip to main content
Question

Is anyone having issues with Figma Make flagging new issues in unchanged code?

  • March 11, 2026
  • 3 replies
  • 47 views

Orome

My Make projet sudenly generates multiple errors and then crashes, including unrecognized DOM elements and duplicate imports, but I've changed nothing since this worked fine about a week ago. Has something changed or broken? Anyone else seeing similar?

 

nternal Server Error
Duplicate declaration "DConfig"
16 | }
17 |
> 18 | export function DConfig({
| ^^^^^^^^^^^^^^^^^^
19 | item,
20 | question,
21 | open,
at File.buildError [as buildCodeFrameError] (node_modules/.pnpm/@babel+core@7.28.4/node_modules/@babel/core/src/transformation/file/file.ts:257:12)
...
Internal Server Error
components/QView.tsx: Identifier 'DConfig' has already been declared. (18:31)

16 | import { Badge } from "./ui/badge";
17 | import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from "./ui/tooltip";
> 18 | import { DQ, DConfig } from "./utils/dUtils";
...
PM [vite] (client) Pre-transform error: components/QView.tsx: Identifier 'DConfig' has already been declared. (18:31)

16 | import { Badge } from "./ui/badge";
17 | import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from "./ui/tooltip";
...
Warning: React does not recognize the `%s` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `%s` instead. If you accidentally passed it from a parent component, remove it from the DOM element.%s _fgT _fgt
at svg
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/chunk-HSIZ2WP3.js?v=c35516da:1611:5
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/chunk-HSIZ2WP3.js?v=c35516da:1643:8
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/chunk-HB4CYL2K.js?v=c35516da:63:11
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/chunk-HB4CYL2K.js?v=c35516da:44:11
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/chunk-27MLYL4D.js?v=c35516da:29:13
at https://app-jforochciqmrpennorpib76uditcuhydsxz7s6syay62lhaca7hq.makeproxy-c.figma.site/node_modules/.vite/deps/@radix-ui_react-select@2__1__6.js?v=ba7f24a2:274:13
```
And many more!

 

This topic has been closed for replies.

3 replies

ksn
Figmate
  • Community Support
  • March 11, 2026

Hey ​@Orome! I believe I came across your reddit post about this over here as well: https://www.reddit.com/r/FigmaDesign/comments/1rr2ovl/is_anyone_having_issues_with_figma_make_flagging/

I mentioned there that I’d follow up with you here as well, just to cover all bases. I’m going to send you a PM for more info. Thank you!


Orome
  • Author
  • New Member
  • March 11, 2026

Yes that’s me. I don’t understand what’s happening. Fortunately I didn't have a presentation scheduled but if I had this would have been fatal!


ksn
Figmate
  • Community Support
  • March 12, 2026

Hey ​@Orome - just wanted to close the loop here, and confirm that our technical quality team is now in possession of your support ticket, and will follow up with you via email. Thank you for your patience!