Connect sign-in

Step 2 of 5. Point the kit at your own Firebase project so Google and email sign-in work for real. Each step here is one command or one console screen; the Sign-in guide owns the detail.

The checklist

1. Install the Firebase CLI and log in: npm i -g firebase-tools, then firebase login.

2. Run the Firebase setup:

   pnpm create extstart --firebase

   It creates or picks a project, writes the SDK config into every file that carries it, and prints deep links for the console steps below (what it writes).

3. Enable the sign-in providers: Google and Email/Password (and Anonymous, if you use anonymous-first) in the console screen the wizard linked (details).

4. Create the Google OAuth client and paste its ID as WXT_GOOGLE_OAUTH_CLIENT_ID when the wizard offers (redirect-URI steps).

5. Upgrade the project to the Blaze plan: step 4 of the journey deploys a Cloud Function, which Spark can’t do. The free-tier quota covers development (details).

6. Rebuild and reload: restart pnpm dev (env values are baked in at build time), then reload the extension on chrome://extensions.

Verify

Open the popup and click Sign in with Google. The “Connect your Firebase project” notice is gone, the OAuth window completes, and your account shows in the Account tab.

If the sign-in window opens and closes without signing you in, the OAuth redirect URI doesn’t match your current extension ID; see the fix. To skip the OAuth client entirely, use the offscreen popup path instead (Chromium only, zero OAuth config); the sign-in guide compares the two paths.

Once you’re signed in, continue to 3. Take payments: seed Stripe and watch that account become a paying customer.