About Fireclass
Fireclass gives Node.js, Express, Next.js, and React applications a shared model API while preserving the security and execution model of each Firebase runtime.
Purpose
Firestore applications often repeat the same work: translate snapshots, preserve document ids, validate writes, rebuild queries, and create separate abstractions for server and client code.
Fireclass centralizes that work behind decorated TypeScript classes and a small adapter contract. Runtime packages connect the same core to Firebase Admin, the Firebase client SDK, and Next.js server boundaries without hiding the underlying Firestore constraints.
The project remains explicit about validation, indexes, Security Rules, credentials, serialization, and unsupported capabilities so application architecture stays understandable.
Design principles
Models, filters, results, adapters, and errors expose explicit TypeScript contracts without generated model code.
The shared core keeps CRUD, validation, and query behavior consistent across server, browser, and test runtimes.
Admin credentials stay on trusted servers, React uses the Firebase client SDK, and Next.js client imports stay dependency-free.
Each package owns one responsibility, publishes its adapter surface, and remains independently testable and replaceable.
Package suite