Check for both Firebase CLIs before configuring, and say how to install them

[seenu-k]

Hit while configuring a freshly scaffolded game:

configure_firebase: could not find `flutterfire`. Install the Firebase and FlutterFire CLIs, then run this command again.

firebase was already installed. FlutterFire was the missing one, and the message neither said so nor gave the command — which matters here more than usual, because FlutterFire does not come with Flutter, and dart pub global activate puts it in a directory that is not on PATH by default. "Install both CLIs" is the least useful thing to say to someone who has one of them.

Now:

configure_firebase: could not find `flutterfire`. Install it with:

  dart pub global activate flutterfire_cli
  …and put Dart's global bin directory on your PATH (~/.pub-cache/bin on macOS and Linux)

Then run this command again.

Checked up front rather than on use

firebase is not reached until FlutterFire has already written firebase.json and lib/firebase_options.dart, so finding out then that it is missing leaves a half-configured app. Both tools are probed before anything runs. The probe ignores exit status — anything other than "no such executable" means the tool is installed, and whatever is wrong with it is better reported by the command that actually needs it.

The old ProcessException handler stays as a fallback for a tool that disappears between the check and its use, and now shares the same message.

Tests

A new case runs the script with a fake firebase on a trimmed PATH and asserts exit 69, that the message names flutterfire and carries the activate command, and that the tool the reader does have stays out of it. The existing end-to-end case is unaffected.

dart analyze clean, both tests pass. CHANGELOG.md has an [Unreleased] entry via cider log.

🤖 Generated with Claude Code