Repository navigation
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listblockedIssue is blocked by another issueIssue is blocked by another issuec: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.fyi-webFor the attention of Web platform teamFor the attention of Web platform teamteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.Issues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team
Description
DDC currently supports three different formats for handling modules: DDC, AMD, and ES6. Flutter Web externally uses the AMD module system, but all of google3 and Flutter Web internally use the DDC module system (due to its greater configurability).
Consolidating module systems will give us more granular control over how libraries are loaded/updated, allowing us to better support features like hot restart, hot reload, and multi-app configurations. We don't expect any major user-visible changes from this.
This will be a multi-step process that will involve:
- Adding DDC module system support to Dart Web tooling (such as DWDS)
- Plumbing DDC module system support through flutter_tools and the engine and locking it behind a flag
- Extending core functionality (hot restart, test runners, etc.) to support the DDC module system to reach feature parity with AMD.
- Enabling the new module system and watching for unexpected changes.
- Cleaning up AMD module system code artifacts
See related issue in the Dart SDK: dart-lang/sdk#52361
Reacted by Parker Lougheed and Fré Dumazy
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listblockedIssue is blocked by another issueIssue is blocked by another issuec: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.fyi-webFor the attention of Web platform teamFor the attention of Web platform teamteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.Issues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team
Activity
[-]Deprecate the AMD module system in Flutter Web[/-][+]Deprecate DDC's AMD module system in Flutter Web[/+]mdebbar commentedon Aug 7, 2025
I believe this is being done within the DDC Hot Reload umbrella. cc @nshahan
flutter-triage-bot commentedon Dec 12, 2025
This issue is assigned to @nshahan but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
nshahan commentedon Dec 12, 2025
I've been waiting for a full release cycle with all the features enabled by default in the new module system so we can assess any feedback we get and then I will deprecate the ability to switch back to the old module system. After a deprecation release I will remove it entirely.
flutter-triage-bot commentedon Apr 17, 2026
This issue is assigned to @nshahan but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
6 remaining items
[flutter_tools] Remove web hot reload flag (flutter#185994)
flutter-triage-bot commentedon Sep 7, 2026
This issue is assigned to @nshahan but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
nshahan commentedon Sep 9, 2026
Still planning on wrapping this up soon. The removal of the opt out flag has now shipped in the stable release so I'm going to cleanup the last remaining support that is totally inaccessible from the users perspective.
Remove webDevFS tests for the AMD module system (flutter#193028)
Cleanup DDC SDK build targets (flutter#193193)
Cleanup unneeded hot restart tests (flutter#193598)
[flutter_tools] Remove the last AMD module system support
[flutter_tools] Remove the last AMD module system support
[flutter_tools] Remove the last AMD module system support (flutter#19…
github-actions commentedon Oct 28, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[flutter_tools] Remove the last AMD module system support (flutter#19…