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.
48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
# minipass-flush
|
|
|
|
A Minipass stream that calls a flush function before emitting 'end'
|
|
|
|
## USAGE
|
|
|
|
```js
|
|
const Flush = require('minipass-flush')
|
|
cons f = new Flush({
|
|
flush (cb) {
|
|
// call the cb when done, or return a promise
|
|
// the 'end' event will wait for it, along with
|
|
// close, finish, and prefinish.
|
|
// call the cb with an error, or return a rejecting
|
|
// promise to emit 'error' instead of doing the 'end'
|
|
return rerouteAllEncryptions().then(() => clearAllChannels())
|
|
},
|
|
// all other minipass options accepted as well
|
|
})
|
|
|
|
someDataSource.pipe(f).on('end', () => {
|
|
// proper flushing has been accomplished
|
|
})
|
|
|
|
// Or as a subclass implementing a 'flush' method:
|
|
class MyFlush extends Flush {
|
|
flush (cb) {
|
|
// old fashioned callback style!
|
|
rerouteAllEncryptions(er => {
|
|
if (er)
|
|
return cb(er)
|
|
clearAllChannels(er => {
|
|
if (er)
|
|
cb(er)
|
|
cb()
|
|
})
|
|
})
|
|
}
|
|
}
|
|
```
|
|
|
|
That's about it.
|
|
|
|
If your `flush` method doesn't have to do anything asynchronous, then it's
|
|
better to call the callback right away in this tick, rather than returning
|
|
`Promise.resolve()`, so that the `end` event can happen as soon as
|
|
possible.
|