545563e776
- Complete NestJS TypeScript implementation with WebSocket support - Direct messaging (DM) and group chat functionality - End-to-end encryption with AES encryption and key pairs - Media file support (images, videos, audio, documents) up to 100MB - Push notifications with Firebase Cloud Messaging integration - Mention alerts and real-time typing indicators - User authentication with JWT and Passport - SQLite database with TypeORM entities and relationships - Comprehensive API documentation with Swagger/OpenAPI - File upload handling with secure access control - Online/offline status tracking and presence management - Message editing, deletion, and reply functionality - Notification management with automatic cleanup - Health check endpoint for monitoring - CORS configuration for cross-origin requests - Environment-based configuration management - Structured for Flutter SDK integration Features implemented: ✅ Real-time messaging with Socket.IO ✅ User registration and authentication ✅ Direct messages and group chats ✅ Media file uploads and management ✅ End-to-end encryption ✅ Push notifications ✅ Mention alerts ✅ Typing indicators ✅ Message read receipts ✅ Online status tracking ✅ File access control ✅ Comprehensive API documentation Ready for Flutter SDK development and production deployment.
@firebase/logger
This package serves as the base of all logging in the JS SDK. Any logging that is intended to be visible to Firebase end developers should go through this module.
Basic Usage
Firebase components should import the Logger class and instantiate a new
instance by passing a component name (e.g. @firebase/<COMPONENT>) to the
constructor.
e.g.
import { Logger } from '@firebase/logger';
const logClient = new Logger(`@firebase/<COMPONENT>`);
Each Logger instance supports 5 log functions each to be used in a specific
instance:
debug: Internal logs; use this to allow developers to send us their debug logs for us to be able to diagnose an issue.log: Use to inform your user about things they may need to know.info: Use if you have to inform the user about something that they need to take a concrete action on. Once they take that action, the log should go away.warn: Use when a product feature may stop functioning correctly; unexpected scenario.error: Only use when user App would stop functioning correctly - super rare!
Log Format
Each log will be formatted in the following manner:
`[${new Date()}] ${COMPONENT_NAME}: ${...args}`