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

51 lines
1.5 KiB
JavaScript

let globalPnpApi;
try {
globalPnpApi = require(`pnpapi`);
} catch {
// Just ignore if we don't have a global PnP instance - perhaps
// we'll eventually find one at runtime due to multi-tree
}
const createRequire = require(`./createRequire`);
const getDefaultResolver = require(`./getDefaultResolver`);
module.exports = (request, options) => {
const {
basedir,
defaultResolver = getDefaultResolver(),
extensions,
} = options;
if (process.versions.pnp) {
let pnpApi = globalPnpApi;
// While technically it would be more correct to run this code
// everytime (since they file being run *may* belong to a
// different dependency tree than the one owning Jest), in
// practice this doesn't happen anywhere else than on the Jest
// repository itself (in the test env). So in order to preserve
// the performances, we can afford a slight incoherence here.
if (!pnpApi) {
try {
const baseReq = createRequire(`${basedir}/internal.js`);
pnpApi = baseReq(`pnpapi`);
} catch {
// The file isn't part of a PnP dependency tree, so we can
// just use the default Jest resolver.
}
}
if (pnpApi) {
const resolution = pnpApi.resolveRequest(request, `${basedir}/`, {extensions});
// When the request is a native module, Jest expects to get the string back unmodified, but pnp returns null instead.
if (resolution === null)
return request;
return resolution;
}
}
return defaultResolver(request, {...options, allowPnp: false});
};