![dependabot-preview[bot]](https://avatars.githubusercontent.com/in/2141?v=4&s=144)
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?v=4&s=144)
Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
62
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · Last activity 4mo ago
See all on GitHub →
Problem keeps subscriptions across snapshots but recreates its resolution counter for each call. If a nested reference changes, disappears, or its collection document is removed or moved before initial resolution, the binding can lose resolution credit and stay pending with . Fix Keep resolution state on persistent subscriptions and notify every waiting snapshot. Rebind indexed reference paths when collection documents move and resolve removed documents. Preserve resolved parent data for nested updates and ignore callbacks from disposed listeners. Tests Added deterministic coverage for path changes, removed documents, disappearing references, collection moves, and nested updates. The full emulator suite will run in CI; the local machine has no Java runtime. Temporary workaround Until this is released, consumers can backport the change with . Explicitly limiting and using bounded waits with direct Firestore reads on critical paths reduce the impact, but do not fix the lifecycle race. Summary by CodeRabbit Bug Fixes** Improved handling of nested Firestore references during document and collection updates. Prevented updates from being processed after listeners are unsubscribed. Improved error handling for synchronous listener callback failures. Preserved resolved reference data across document moves, removals, reordering, and nested updates. Removed documents now resolve with their final document data. Prevented duplicate resolution and stale subscription data during reference changes.
What Widens the peer dependency range of to include : Why already accepts as a peer, but does not, so installing a project with fails: The module only uses stable APIs (, , session cookie verification, app-check), which are unchanged in v14 — the major was primarily dropping Node 18 support. 🤖 Generated with Claude Code Summary by CodeRabbit Chores Expanded compatibility by updating the declared minimum Node.js version to >= 22. Expanded compatibility with additional supported Firebase Admin SDK versions (now includes ^14.0.0** alongside existing versions).
Reproduction https://github.com/posva/nuxt--vuefire-example-spark-plan Steps to reproduce the bug 1. trigger signInWithRedirect(provider) from firebase auth. 2. redirect to the oauth provider (e.g., twitter). 3. sign in successfully. 4. user is redirected back but not logged in. 5. no persistent auth state or missing result from getRedirectResult(). https://github.com/user-attachments/assets/dceb478f-5405-4851-8e5b-b827527b597f Expected behavior after returning from the oauth provider, calling getRedirectResult() should yield the current user state and the auth state should persist across reloads. Actual behavior the app reloads and useCurrentUser() returns null getRedirectResult() doesn't resolve the user persistence appears broken, even when set to local Additional information signInWithPopup() works fine
Recent fixes
Pins the default to on 1 workflows in that don't call a GitHub API beyond the initial checkout. Left implicit because they reference / use a write-scope action / trigger on . Best declared by a maintainer: , . Why CVE-2025-30066 (March 2025 supply-chain compromise) exfiltrated from workflow logs. Pinning per workflow caps runtime authority irrespective of the repo or org default, gives drift protection if the default ever widens, and is credited per-file by the OpenSSF Scorecard check. YAML validated locally with on each touched file. Summary by CodeRabbit Chores** Tightened automated workflow security by restricting CI token permissions to read-only for repository contents, reducing exposure of write-level access.
Summary by CodeRabbit Chores Updated Firebase Functions dependency to v7.0.0 Expanded Firebase Functions version compatibility in Nuxt package to include v7.0.0 Updated CI workflow to use Java 21 Tests Refactored Firestore collection tests for improved test isolation ✏️ Tip: You can customize this high-level summary in your review settings.
Reproduction Steps to reproduce the bug 1. Create a new Nuxt project (or use an existing one). 2. Install Firebase Functions v7: 3. Install VueFire for Nuxt: 4. Observe the dependency resolution error. Expected behavior should install successfully and support the latest Firebase Functions release () without requiring or . Actual behavior Installation fails due to a peer dependency conflict: npm ERR! ERESOLVE could not resolve npm ERR! While resolving: nuxt-vuefire@1.1.0 npm ERR! Found: firebase-functions@7.0.0 npm ERR! node_modules/firebase-functions npm ERR! firebase-functions@"^7.0.0" from the root project npm ERR! Could not resolve dependency: npm ERR! peerOptional firebase-functions@"^4.1.0 ^6.1.2" from nuxt-vuefire@1.1.0 npm ERR! Conflicting peer dependency: firebase-functions@6.6.0 npm ERR! peerOptional firebase-functions@"^4.1.0 ^6.1.2" from nuxt-vuefire@1.1.0 Additional information Recent Firebase Functions release:\ https://github.com/firebase/firebase-functions/releases/tag/v7.0.0 currently lists only: ^4.1.0 ^6.1.2 Suggested peer dependency update: ^4.1.0 ^7.0.0
Structured data for AI agents
Repository: vuejs/vuefire. Description: 🔥 Firebase bindings for Vue.js Stars: 3909, Forks: 340. Primary language: TypeScript. Languages: TypeScript (86.7%), Vue (9.7%), JavaScript (2%), CSS (0.8%), EJS (0.6%). License: MIT. Homepage: https://vuefire.vuejs.org Topics: database, firebase, firestore, nuxt, pinia, realtime, vue, vuex. Latest release: nuxt-vuefire@1.1.2 (4mo ago). Open PRs: 20, open issues: 26. Last activity: 4mo ago. Community health: 62%. Top contributors: posva, dependabot-preview[bot], greenkeeper[bot], trickstival, davidstackio, danielroe, luc122c, sweethuman, i5dr0id, dependabot[bot] and others.