@timonwa/firebase-hooks@0.2.0

Minor Changes

• #20 ca73117 Thanks @Timonwa! - The auth argument is now optional. Below an AuthProvider, hooks take the instance from it, so an app no longer names the same object at every call site:

  const { login } = useLogin();
  const { signup } = useSignup({ sendVerificationEmail: false });

  Passing your own still works and overrides the provider's — what you need for a second Firebase project, or with no provider at all. null keeps its existing meaning of "not ready yet, don't run", so a hook held back while Firebase initialises never silently runs against the provider's instance instead.

  Breaking: useUpdatePassword and useUpdateEmail take the new value positionally, matching the Firebase SDK they wrap and useSignup's existing shape.

  // Before
  await update({ newPassword, currentPassword });
  await update({ newEmail, currentPassword });
  
  // After
  await update(newPassword, { currentPassword });
  await update(newEmail, { currentPassword });

  Firebase's own updatePassword(user, newPassword) and verifyBeforeUpdateEmail(user, newEmail) lead with the required value; currentPassword is the reauthentication these hooks add on top, so it belongs in the options bag after it. useUpdateProfile is unchanged — its fields are all optional, which is why the SDK passes them as an object too.

  Nothing else changes: every existing useLogin(auth, options) call keeps working.

Patch Changes

• #15 f6c4950 Thanks @Timonwa! - Point homepage at the documentation site rather than the GitHub readme anchor, so the npm sidebar links somewhere with a page per hook.

v0.1.0

Minor Changes

• #11 fe2779c Thanks @Timonwa! - Initial release. Typed React hooks for Firebase, one import per service. This release covers the shared core and the Auth service; Firestore and Storage follow.

  Auth — @timonwa/firebase-hooks/auth

  • AuthProvider / useAuth — live user and custom claims via onIdTokenChanged, plus app-wide defaults.
  • Sign in — useLogin, useSignup, useOAuthSignIn (popup or redirect, redirect completed on return), useEmailLinkSignIn (needsEmail instead of window.prompt), usePhoneSignIn (managed reCAPTCHA, recaptchaSize option), useAnonymousSignIn, useCustomTokenSignIn, useLogout (your session teardown runs first).
  • Passwords — useSendPasswordResetEmail, useConfirmPasswordReset (with verifyCode), useUpdatePassword.
  • Email — useVerifyEmail, useSendEmailVerification, useUpdateEmail.
  • Account — useUpdateProfile, useDeleteAccount, useReauthenticate, useLinkProvider, useUnlinkProvider.
  • AUTH_ERROR_MESSAGES — a curated auth/* message catalogue, applied only if you opt in.

  Core — @timonwa/firebase-hooks

  formatFirebaseError, getFirebaseErrorCode, and the shared HookResult, HookErrorOptions, HookErrorContext, FormatFirebaseErrorOptions, and OnIdToken types.

  How it behaves

  • Actions never throw. Each resolves to { success: true, ... } or { success: false, error, code, cause }, where error is Firebase's own message unless you opt into formatting, and cause is the untouched error.
  • Sign-in successes hand back Firebase's raw UserCredential alongside the user.
  • Server sessions plug in through onIdToken and onBeforeSignOut; throw inside either to abort the flow.
  • onIdToken, onBeforeSignOut, actionCodeSettings, formatErrorMessage, and a fire-and-forget onError(error, { action, code, message }) observer are set once on AuthProvider; any hook can override them or opt out with null.
  • Sensitive operations reauthenticate when given currentPassword, and work without it for OAuth-only accounts.

  Zero dependencies — firebase and react are peers. Ships ESM and CJS with type declarations and a "use client" banner.

@timonwa/firebase-hooks@0.1.1

Patch Changes

• #13 c905822 Thanks @Timonwa! - Document every hook option in the published types. Each Use<Name>OptionsProps field now carries TSDoc, with its default where it has one, so editors show what an option does at the call site instead of only its type.

  Also exposes ./package.json as a subpath export, so tooling can read the version without reaching into the package directory.

  No runtime change — every hook behaves exactly as before.