RFC: v1 roadmap

next-firebase-auth has been reasonably stable for a while now and is already used in production apps, so it feels an appropriate time to move toward a v1 release.

This is an in-progress document of the changes that might land in v1. Please comment with any feedback or questions.

The unstable releases are available as next-firebase-auth@canary. When contributing, please make pull requests to the v1.x branch.

Demo: the demo app is deployed here.

---

Prerequisites

• Set up a canary/next/v1 branch and release process (@kmjennison)
• Set up a canary live demo (@kmjennison)

Making the package work better

• #164
  • Drop support for Firebase <9
• #174
• Fix bug with HMR: #163
  • Potentially via #207
• #142
• #488

Making the package more flexible

• ~#190~ Deferred: we’ll delay this to a potential later release because 1) we won’t want to complicate adoption of Firebase v9, 2) we haven’t identified a suitable cookies library, and 3) this library might have a cookie-free future (see #287).
  • Identify a suitable cookies library
  • Identify a clear migration strategy for existing apps to avoid cookie mismatches
  • Implement
  • Write migration documents
• #223
• #233
• #444

Preventing incorrect use

• #155
• #195

Developer tools

• #389

Cleanup

• Make API name changes
  • Instances of AuthUser: AuthUser --> user
  • withAuthUser --> withUser
  • withAuthUserTokenSSR --> withUserTokenSSR
  • withAuthUserSSR --> withUserSSR
  • useAuthUser --> useUser

Before release

• #296
• If needed, provide a codemod (jscodeshift)
• Write migration guide
• Ensure README is up to date

[HofmannZ]

Hi, I’m picking up Firebase v9 support 👨‍💻

[DiegoGonzalezCruz]

Hi guys, hope everything is going great. I am wondering if you have an estimated ETA for v1?