Firebase-style code (Firestore API)

@sovaria/sdk/firestore has the functions of Firebase's modular Firestore API on top of Sovaria documents, so moving an app is an import change. Queries, live listeners, batches and transactions are the real Sovaria ones described in Querying documents, Live listeners and Transactions, batches and field transforms.

import { initializeApp } from 'firebase/app'
import { getFirestore, collection, query, where, orderBy, limit, onSnapshot } from 'firebase/firestore'

const db = getFirestore(initializeApp(firebaseConfig))

#What is supported

#Differences from Firebase

• Times are stored as ISO-8601 strings. Timestamp, Date and serverTimestamp() all become one, so ordering and range filters work; read them back with new Date(value) or Timestamp.fromDate(new Date(value)).
• Offline persistence works the Firebase way — initializeFirestore(sov, { localCache: persistentLocalCache() }) or enableIndexedDbPersistence(db) — and snapshots report metadata.fromCache and metadata.hasPendingWrites. Multi-tab coordination isn't there yet: use one tab per app, or each tab keeps its own queue. See Offline-first apps.
• Access is decided by your collection rules and row policies, not firestore.rules. sov import firebase --rules firestore.rules writes a report of the equivalent of each rule. See Documents.
• One rule covers a subcollection under every document: write the path with * for the document id, like users/*/orders. A * stands for exactly one path segment and the depth must match, so users/*/orders covers users/alice/orders but not users/alice or users/alice/orders/o1/items. In a policy, compare ctx.resource.pattern (ALLOW IF ctx.resource.pattern == "users/*/orders"); ctx.resource.name keeps the full path. Permission claims work the same way: collection:users/*/orders:read.
• Document ids and collection names use letters, digits, _ . @ - (up to 256). The Firebase import cleans other characters and lists every renamed id.

Moving the data too: Migrate from Supabase or Firebase imports Firebase Auth users with their passwords, every collection and subcollection at the same paths, and Storage files.