[Figma Plugin] Exported ui-components now include broken imports after recent plugin update (since late Sep 2025)

[kdl-kawata]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have tried disabling all browser extensions or using a different browser
• I have tried deleting the node_modules folder and reinstalling my dependencies
• I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

React

Which UI component?

Primitive components

How is your app built?

Next.js

What browsers are you seeing the problem on?

No response

Which region are you seeing the problem in?

No response

Please describe your bug.

Summary

After the recent update of the AWS Amplify UI Builder plugin for Figma (around September 26, 2025), the exported ui-components code differs from previous versions and now fails to build in React.

When comparing exports from September 17, 2025 (working) and November 5, 2025 (broken), the new export includes invalid imports referencing files that do not exist.
No changes were made to the Figma design file itself — only the plugin appears to have changed behavior.

---

Environment / Setup

• Figma plugin: AWS Amplify UI Builder
• Figma file structure:
  • Using Primitives (base Amplify UI components) provided by the plugin
  • Custom components created under My components page
• Export method:
  Run “Download component code” → output placed under /ui-components in React project
  (No manual edits applied to generated files)

---

Problem

When exporting with the latest plugin:

• The generated component imports nonexistent files, e.g.:

  import { TextField1RMCProps } from "./TextField1RMC";
  import { SelectFieldRMCProps } from "./SelectFieldRMC";
  import { TextField1Props } from "./TextField1";
  import { TextFieldMoveinBlockRMCProps } from "./TextFieldMoveinBlockRMC";
  import { RadioDayMoveinBlockRMCProps } from "./RadioDayMoveinBlockRMC";

• These files do not exist in the generated folder.

• In React build:

  Cannot find module './TextField1RMC' or its corresponding type declarations.
  

• In addition, some previously unaffected components now include new imports like:

  import { RadioYProps } from "./RadioY";
  import { RadioTProps } from "./RadioT";
  import { TextFieldStartADProps } from "./TextFieldStartAD";
  import { TextFieldEndADProps } from "./TextFieldEndAD";

  which did not appear in older exports.

---

Verification

• The Figma design was rolled back to the version as of 2025/09/17 using Figma’s version history, then re-exported —
  → identical problem still occurred.
  → Therefore, the cause is not the design file but the plugin update.

• Verified that:

  • The component correctly references a Primitive as its parent (via “Go to main component”)
  • No structural or naming changes were made in Figma.

---

Possible Cause (Hypothesis)

• The plugin update released around 2025/09/26 may have changed the code generation logic for ui-components.
• The updated version seems to treat internal layers or reused elements as if they were separate child components, leading to missing imports.

Reference:
🔗 https://www.figma.com/community/plugin/1040722185526429545/aws-amplify-ui-builder

---

Requests

1. Please confirm the recent update history and code generation changes of the Figma plugin.
2. Please advise how to generate the same ui-components output as before the update (as of Sep 17, 2025).
3. If possible, consider providing an option to use or select an older stable plugin version for projects that depend on consistent code generation.

---

Environment Information

Item	Detail
Plugin version	AWS Amplify UI Builder (latest as of 2025/11/05)
Figma app version	124.3.5 (Desktop)
OS	macOS 14.5 / Windows 11
Amplify UI library	@aws-amplify/ui-react@^6
Framework	React + TypeScript
Working export	2025-09-17
Broken export	2025-11-05

---

Attachments

• Screenshot comparing Sept 17 and Nov 5 exports (showing invalid imports)
• Figma design file available upon request for reproducibility

---

Notes

We appreciate the recent improvements to the plugin, but this change breaks existing build pipelines.
We would appreciate confirmation on whether this behavior change was intentional or a regression.

What's the expected behaviour?

The ui-components exported from the AWS Amplify UI Builder Figma plugin should generate valid, buildable React code — the same structure as previous exports before late September 2025.

Specifically:

• Each generated component should only import existing files.
• Components that use Primitives (such as TextField, Button, or Flex) should reference them correctly from @aws-amplify/ui-react, not as local files.
• The same Figma design (rolled back to Sep 17, 2025) should produce identical ui-components output and should build successfully with no missing imports.

Help us reproduce the bug!

1. Open Figma and enable the AWS Amplify UI Builder plugin.
2. Create or open a design that includes:
   • A few components under My components.
   • Each uses Primitives (e.g., Flex, Text, Button) as building blocks.
3. Run “Download component code” from the plugin.
4. Place the exported ui-components folder into a React project.
5. Run npm run build (or npx tsc --noEmit).

🧩 Result:
The build fails with errors like:

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

ResidentReport1SP.d.ts-diff.htm

[jvh-aws]

Thanks for reporting the issue! We are currently investigating. I tried to reproduce the issue that you are describing, but using the steps that you are providing, I cannot reproduce the error. Could you kindly provide us with a stripped down version of your file (no confidential data) that allows us to reproduce the issue? If you prefer, you can also directly share it with our plugin support email aws-amplify-uibuilder@amazon.com

[kdl-kawata]

I've attached a simplified Figma file.
When you export using Amplify UI Builder, you can confirm that "TextField1RMC" is the problem in question.
AWS_Amplify_UI_Kit_1113.zip

[jvh-aws]

Thanks for sharing @kdl-kawata! I have verified that we're receiving the same output that you report on your file with both the most recent as well as the pre-September version of the plugin.

It appears to me, that in your file, the second text input field (in your component, TestField-test2 > TextField1RMC) has a broken link to the main component. When right-clicking it, I receive an error You don't have access to this file. Hence, I assume that the link to the main component is broken. Can you please try to copy the broken primitive into the component again?

[kdl-kawata]

Additional Explanation of the Issue

To help explain the issue, I am sharing a new Figma file.
This file contains the following three types of components:
AWS_Amplify_UI_Kit_1117.zip

1. test1 (TextField-test1)
The parent component references the Primitives inside this Figma file.

Exporting with the Amplify UI Builder works without any issues
(no imports for non-existent files are generated).

2. test2 (TextField-test2)
The parent component references Primitives from another Figma file.

Exporting with the Amplify UI Builder results in an issue
(imports for non-existent files are generated).

3. test3 (TextField-test3)
The parent component references a component in My Components
(which is a copy of a Primitive from another Figma file).

Exporting with the Amplify UI Builder also results in an issue
(imports for non-existent files are generated).

Background and Additional Details
In the file I attached previously, the second text field was in the same condition as test2 (TextField-test2).
Since you do not have access permissions to the referenced Figma file, I suspect that the link appears broken on your side.
(From my account, the parent component reference is intact.)

Additionally, before September 17, 2025, components in the test2 state were exported correctly — without generating imports for missing files.

Question
Is it possible to restore the previous behavior so that components in the test2 (TextField-test2) state can be exported without generating imports for non-existent files, as was the case before?