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.
accepts
Higher level content negotiation based on negotiator. Extracted from koa for general use.
In addition to negotiator, it allows:
- Allows types as an array or arguments list, ie
(['text/html', 'application/json'])as well as('text/html', 'application/json'). - Allows type shorthands such as
json. - Returns
falsewhen no types match - Treats non-existent headers as
*
Installation
This is a Node.js module available through the
npm registry. Installation is done using the
npm install command:
$ npm install accepts
API
var accepts = require('accepts')
accepts(req)
Create a new Accepts object for the given req.
.charset(charsets)
Return the first accepted charset. If nothing in charsets is accepted,
then false is returned.
.charsets()
Return the charsets that the request accepts, in the order of the client's preference (most preferred first).
.encoding(encodings)
Return the first accepted encoding. If nothing in encodings is accepted,
then false is returned.
.encodings()
Return the encodings that the request accepts, in the order of the client's preference (most preferred first).
.language(languages)
Return the first accepted language. If nothing in languages is accepted,
then false is returned.
.languages()
Return the languages that the request accepts, in the order of the client's preference (most preferred first).
.type(types)
Return the first accepted type (and it is returned as the same text as what
appears in the types array). If nothing in types is accepted, then false
is returned.
The types array can contain full MIME types or file extensions. Any value
that is not a full MIME types is passed to require('mime-types').lookup.
.types()
Return the types that the request accepts, in the order of the client's preference (most preferred first).
Examples
Simple type negotiation
This simple example shows how to use accepts to return a different typed
respond body based on what the client wants to accept. The server lists it's
preferences in order and will get back the best match between the client and
server.
var accepts = require('accepts')
var http = require('http')
function app (req, res) {
var accept = accepts(req)
// the order of this list is significant; should be server preferred order
switch (accept.type(['json', 'html'])) {
case 'json':
res.setHeader('Content-Type', 'application/json')
res.write('{"hello":"world!"}')
break
case 'html':
res.setHeader('Content-Type', 'text/html')
res.write('<b>hello, world!</b>')
break
default:
// the fallback is text/plain, so no need to specify it above
res.setHeader('Content-Type', 'text/plain')
res.write('hello, world!')
break
}
res.end()
}
http.createServer(app).listen(3000)
You can test this out with the cURL program:
curl -I -H'Accept: text/html' http://localhost:3000/