File Firebase under running the app rather than deploying it - #18
Merged
Conversation
The two CLI installs were documented in full — commands, the PATH export, a version check — under "To deploy it", which opened by saying neither was needed until you deploy. That is false: a scaffolded app throws `Firebase is not configured` the moment it launches, because identity is how a player gets a seat. The page told readers to skip a step they needed, and they did. Firebase now has its own heading under "To run the app", ahead of the platform toolchains, and says plainly that it is not deferrable. "To deploy it" is Cloudflare alone, which genuinely is. The intro no longer claims nothing installs globally, and the check block no longer frames the two CLIs as something only a reader who has already set up Firebase would run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The two Firebase CLIs were documented in full — install commands, the
PATHexport, a version check — under "To deploy it", a section that opened with:That is false. A scaffolded app throws
Firebase is not configuredthe moment it launches, because identity is how a player gets a seat. The page told a reader following the local development path to skip a step they needed, and they did — which is how this was found.Changes
PATHnote now says why it is needed —dart pub global activatedoes not write it — rather than only what to do if the shell cannot findflutterfire.firebase --version/flutterfire --versionas something only a reader who has already set up Firebase would run.No content was deleted — the install commands,
PATHexport and links to Configure a game and Push notifications all move intact.Lint and a full build pass locally, link checker included.
🤖 Generated with Claude Code