Websocket endpoint

[gloskull]

Pull Request: feat: Scaffold mock WebSocket server for frontend integration

Description

This PR introduces a mock WebSocket server to provide the frontend team with an active WebSocket endpoint for early development and integration. By scaffolding the server before the real-time backend implementation is complete, frontend developers can immediately begin connecting client sockets, testing connection lifecycles, and validating real-time communication workflows without being blocked by pending backend features.

In addition to the WebSocket scaffold, this PR resolves several project environment issues that were affecting development and testing. These include fixing Prisma BOM-related problems, correcting module import inconsistencies, and repairing a failing integration test to restore a clean and stable development environment.

Changes Made

✅ New Features

• Mock WebSocket server: Added a basic WebSocket server implementation in server.js.
• Real-time heartbeat messages: Configured the server to broadcast a JSON heartbeat message to every connected client every 5 seconds.
• Frontend integration support: Provides an immediately usable socket endpoint so frontend developers can begin implementing and testing their WebSocket clients before the production implementation is available.

✅ Environment & Maintenance

• Resolved Prisma Byte Order Mark (BOM) issues affecting the project environment.
• Fixed module import inconsistencies to ensure reliable application startup.
• Repaired a broken integration test to restore a healthy and maintainable test suite.
• Improved overall project stability for local development and CI workflows.

✅ Files Modified

• server.js: Added the mock WebSocket server and periodic ping broadcast functionality.
• Environment configuration files: Updated to resolve Prisma BOM and import-related issues.
• Integration test files: Fixed failing test cases and restored successful execution.

WebSocket Behavior

Broadcast Message

Every five seconds, the server broadcasts the following payload to all connected clients:

{
  "type": "ping",
  "timestamp": "2024-01-15T10:30:00.000Z"
}

This heartbeat allows frontend applications to:

• Verify successful WebSocket connections.
• Test message handling logic.
• Validate automatic reconnection behavior.
• Simulate real-time communication during development.

Testing

WebSocket Testing

• ✅ Verified successful client connections.
• ✅ Confirmed periodic heartbeat broadcasts every 5 seconds.
• ✅ Validated JSON message format.
• ✅ Tested multiple simultaneous client connections.

Environment Verification

• ✅ Prisma environment issues resolved.
• ✅ Module imports functioning correctly.
• ✅ Integration tests executing successfully.
• ✅ Development environment starts without errors.

Benefits

1. Frontend Productivity: Enables frontend development without waiting for the complete backend WebSocket implementation.
2. Parallel Development: Allows frontend and backend teams to work independently while maintaining integration compatibility.
3. Stable Development Environment: Resolves configuration issues that could interrupt developer workflows.
4. Improved Code Quality: Restores passing integration tests and maintains a clean codebase.
5. Future Readiness: Establishes the foundation for replacing the mock implementation with the production WebSocket service.

Security & Validation

• WebSocket messages follow a consistent JSON structure.
• Heartbeat broadcasts are lightweight and suitable for development purposes.
• Existing application behavior remains unchanged outside the mock server functionality.
• Environment fixes improve reliability without introducing breaking changes.

Testing Instructions

1. Start the development server.
2. Connect a WebSocket client to the mock server.
3. Verify that a heartbeat message is received every 5 seconds.
4. Run the project's integration tests and confirm they pass successfully.
5. Confirm that the application starts without Prisma or module import errors.

Checklist

• Mock WebSocket server implemented.
• Periodic heartbeat messages broadcasting correctly.
• Frontend socket integration enabled.
• Prisma environment issues resolved.
• Module import issues fixed.
• Broken integration test repaired.
• Existing functionality preserved.
• No breaking changes introduced.

Issue Resolution

Closes #60 Scaffold mock WebSocket server for frontend integration

This implementation provides a temporary yet functional WebSocket endpoint that allows frontend developers to begin integrating and testing real-time features immediately. Alongside the mock server, several environment and testing issues have been resolved, resulting in a cleaner, more stable, and development-ready codebase while the production WebSocket implementation is being developed.

[gloskull]

Done with this issue.
Please merge and give and high review.
Please if there are any more tasks, assign them to me, i'd make sure to get them done quickly and submit my PR's in under 5 hours