René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ng add` never writes `.firebaserc` or Firestore starter files — deploys have no default project and no rules","articleBody":"### Version info\n\n**Angular:** 21.2.x   **Firebase:** 12.x   **AngularFire:** 21.0.0-rc.0\n\n### How to reproduce these conditions\n\n1. `ng new my-app \u0026\u0026 cd my-app`\n2. `ng add @angular/fire@next`, sign in, select a project and Firestore.\n3. After the schematic finishes: `.firebaserc` does not exist (the project selected during setup is recorded nowhere), `firebase.json` is `{}` (see #3559), and no `firestore.rules` exists.\n\n### Expected behavior\n\nThe setup should leave the workspace deployable: record the selected project as the CLI default, and — when Firestore is selected — generate starter security rules plus the `firebase.json` firestore section, the way `firebase init firestore` does.\n\n### Actual behavior\n\nEvery later firebase-tools command prompts for (or fails without) a project, and `firebase deploy --only firestore:rules` has nothing to deploy. Related downstream reports: #3559 (empty firebase.json, closed unfixed), #3546/#3676 (`ng deploy` setup loop — the angular.json deploy-target half, out of scope here).\n","author":{"url":"https://github.com/armando-navarro","@type":"Person","name":"armando-navarro"},"datePublished":"2026-07-15T18:58:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3713/angularfire/issues/3713"}