René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ng add` crashes with `ReferenceError: e is not defined` instead of warning when dataconnect.yaml cannot be parsed","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. A workspace whose `firebase.json` has a `dataconnect.source` entry, where the referenced `dataconnect.yaml` (or its connector's `connector.yaml`) is missing, unreadable, or malformed.\n2. Run `ng add @angular/fire` so the setup schematic calls `parseDataConnectConfig`.\n\n### Expected behavior\n\nThe parse failure is caught and logged (\"Couldn't parse dataconnect.yaml\" plus the underlying error), and setup continues with the Data Connect config treated as absent — which is what the catch handler is written to do.\n\n### Actual behavior\n\nThe catch handler names its error variable `_` but logs `e`, which is not defined (`src/schematics/utils.ts:379`):\n\n```ts\n} catch (_) {\n  console.error(\"Couldn't parse dataconnect.yaml\", e);\n  return null;\n}\n```\n\nEvaluating `e` throws `ReferenceError: e is not defined` from inside the catch, so the schematic crashes with an error that points nowhere near the actual problem (the YAML). Nothing typechecks this file today — the library build excludes the schematics and esbuild doesn't check types — which is how the undefined identifier survived. Introduced in #3638.\n","author":{"url":"https://github.com/armando-navarro","@type":"Person","name":"armando-navarro"},"datePublished":"2026-07-09T17:14:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3710/angularfire/issues/3710"}