request: Replace the unmaintained `interact` package

[woteska]

Is there an existing feature request for this?

• I have searched the existing issues.

Command

No response

Description

flutterfire_cli 1.4.0 cannot be used as a project dev_dependency in Flutter apps using current stable flutter_localizations, because its interact -> dart_console dependency chain constrains intl to ^0.17.0 || ^0.18.0, while Flutter stable pins/requires intl 0.20.2

my_awesome_project
 ├─ intl 0.20.2
 └─ dev_dependencies:
    └─ flutterfire_cli 1.4.0
       └─ interact ^2.2.0
          └─ dart_console ^1.1.2
             └─ intl ^0.17.0 vagy ^0.18.0

Resolving dependencies...
    Because flutterfire_cli 1.4.0 depends on interact ^2.2.0 and no versions of interact match >2.2.0 <3.0.0, flutterfire_cli 1.4.0 requires interact 2.2.0.
(1) So, because interact 2.2.0 depends on dart_console ^1.1.2, flutterfire_cli 1.4.0 requires dart_console ^1.1.2.

    Because dart_console 1.2.0 depends on intl ^0.18.0 and dart_console >=1.1.0-pre.0 <1.2.0 depends on intl ^0.17.0, dart_console >=1.1.0-pre.0 <=1.2.0 requires intl ^0.17.0 or ^0.18.0.
    And because no versions of dart_console match >1.2.0 <2.0.0, dart_console ^1.1.0-pre.0 requires intl ^0.17.0 or ^0.18.0.
    And because flutterfire_cli 1.4.0 requires dart_console ^1.1.2 (1), flutterfire_cli 1.4.0 requires intl ^0.17.0 or ^0.18.0.
    So, because my_awesome_project depends on both intl 0.20.2 and flutterfire_cli 1.4.0, version solving failed.
Failed to update packages.

Suggestion: replace interact, because it is no longer maintained enough for current Dart/Flutter dependency constraints (latest release was 3 years ago)

This makes flutterfire_cli difficult to use in modern Flutter projects and CI pipelines, even though the CLI itself is only a development/build-time tool.

Reasoning

Replacing the unmaintained interact dependency would make flutterfire_cli compatible with current Flutter stable projects and avoid forcing users to add risky dependency overrides or maintain internal forks.

Additional context and comments

No response