backend.im/realtimechatapiwithmediasupport-t50lz6

History

Automated Action 545563e776 Implement comprehensive real-time chat API with NestJS

- 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.

2025-06-21 17:13:05 +00:00

index.d.ts

Implement comprehensive real-time chat API with NestJS

2025-06-21 17:13:05 +00:00

index.js

Implement comprehensive real-time chat API with NestJS

2025-06-21 17:13:05 +00:00

license

Implement comprehensive real-time chat API with NestJS

2025-06-21 17:13:05 +00:00

package.json

Implement comprehensive real-time chat API with NestJS

2025-06-21 17:13:05 +00:00

readme.md

Implement comprehensive real-time chat API with NestJS

2025-06-21 17:13:05 +00:00

readme.md

is-unicode-supported

Detect whether the terminal supports Unicode

This can be useful to decide whether to use Unicode characters or fallback ASCII characters in command-line output.

Note that the check is quite naive. It just assumes all non-Windows terminals support Unicode and hard-codes which Windows terminals that do support Unicode. However, I have been using this logic in some popular packages for years without problems.

Install

$ npm install is-unicode-supported

Usage

const isUnicodeSupported = require('is-unicode-supported');

isUnicodeSupported();
//=> true

API