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.
19 lines
809 B
JavaScript
19 lines
809 B
JavaScript
// ESM Exports
|
|
// ===========
|
|
// This module is the package entry point for ES module users. In other words,
|
|
// it is the module they are interfacing with when they import from the whole
|
|
// package instead of from a submodule, like this:
|
|
//
|
|
// ```js
|
|
// import { map } from 'underscore';
|
|
// ```
|
|
//
|
|
// The difference with `./index-default`, which is the package entry point for
|
|
// CommonJS, AMD and UMD users, is purely technical. In ES modules, named and
|
|
// default exports are considered to be siblings, so when you have a default
|
|
// export, its properties are not automatically available as named exports. For
|
|
// this reason, we re-export the named exports in addition to providing the same
|
|
// default export as in `./index-default`.
|
|
export { default } from './index-default.js';
|
|
export * from './index.js';
|