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.
90 lines
2.3 KiB
TypeScript
90 lines
2.3 KiB
TypeScript
declare namespace npmRunPath {
|
|
interface RunPathOptions {
|
|
/**
|
|
Working directory.
|
|
|
|
@default process.cwd()
|
|
*/
|
|
readonly cwd?: string;
|
|
|
|
/**
|
|
PATH to be appended. Default: [`PATH`](https://github.com/sindresorhus/path-key).
|
|
|
|
Set it to an empty string to exclude the default PATH.
|
|
*/
|
|
readonly path?: string;
|
|
|
|
/**
|
|
Path to the Node.js executable to use in child processes if that is different from the current one. Its directory is pushed to the front of PATH.
|
|
|
|
This can be either an absolute path or a path relative to the `cwd` option.
|
|
|
|
@default process.execPath
|
|
*/
|
|
readonly execPath?: string;
|
|
}
|
|
|
|
interface ProcessEnv {
|
|
[key: string]: string | undefined;
|
|
}
|
|
|
|
interface EnvOptions {
|
|
/**
|
|
Working directory.
|
|
|
|
@default process.cwd()
|
|
*/
|
|
readonly cwd?: string;
|
|
|
|
/**
|
|
Accepts an object of environment variables, like `process.env`, and modifies the PATH using the correct [PATH key](https://github.com/sindresorhus/path-key). Use this if you're modifying the PATH for use in the `child_process` options.
|
|
*/
|
|
readonly env?: ProcessEnv;
|
|
|
|
/**
|
|
Path to the current Node.js executable. Its directory is pushed to the front of PATH.
|
|
|
|
This can be either an absolute path or a path relative to the `cwd` option.
|
|
|
|
@default process.execPath
|
|
*/
|
|
readonly execPath?: string;
|
|
}
|
|
}
|
|
|
|
declare const npmRunPath: {
|
|
/**
|
|
Get your [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) prepended with locally installed binaries.
|
|
|
|
@returns The augmented path string.
|
|
|
|
@example
|
|
```
|
|
import * as childProcess from 'child_process';
|
|
import npmRunPath = require('npm-run-path');
|
|
|
|
console.log(process.env.PATH);
|
|
//=> '/usr/local/bin'
|
|
|
|
console.log(npmRunPath());
|
|
//=> '/Users/sindresorhus/dev/foo/node_modules/.bin:/Users/sindresorhus/dev/node_modules/.bin:/Users/sindresorhus/node_modules/.bin:/Users/node_modules/.bin:/node_modules/.bin:/usr/local/bin'
|
|
|
|
// `foo` is a locally installed binary
|
|
childProcess.execFileSync('foo', {
|
|
env: npmRunPath.env()
|
|
});
|
|
```
|
|
*/
|
|
(options?: npmRunPath.RunPathOptions): string;
|
|
|
|
/**
|
|
@returns The augmented [`process.env`](https://nodejs.org/api/process.html#process_process_env) object.
|
|
*/
|
|
env(options?: npmRunPath.EnvOptions): npmRunPath.ProcessEnv;
|
|
|
|
// TODO: Remove this for the next major release
|
|
default: typeof npmRunPath;
|
|
};
|
|
|
|
export = npmRunPath;
|