Skip to content

Use dependency graph to determine plugin initialization order #99153

Description

@stuartmorgan-g

Currently the initialization order of plugins is arbitrary (probably alphabetical right now); we should use the package dependency graph to initialize them in an order that matches the dependencies in case there are registration-time calls between them.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    P2Important issues not at the top of the work list
    on Feb 25, 2022
  2. added
    a: pluginsSupport for writing, building, and running plugin packages
    on Feb 9, 2023
  3. added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jul 11, 2025
  4. added a commit that references this issue on Oct 1, 2026
    086a6c8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: pluginsSupport for writing, building, and running plugin packagesteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions