radziel/spotlightcam
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ac64afa8512e6461208d042b25e2bfa1b1e5b4bf
spotlightcam/backend/package.json

53 lines
1.2 KiB
JSON
Raw Normal View History

feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
{
"name": "spotlightcam-backend",
"version": "1.0.0",
"description": "Backend API for spotlight.cam - P2P video exchange for dance events",
"main": "src/server.js",
"scripts": {
"start": "node src/server.js",
"dev": "nodemon src/server.js",
"test": "jest --coverage",
feat: add PostgreSQL database with Prisma ORM Phase 1 - Step 2: PostgreSQL Setup **Infrastructure:** - Add PostgreSQL 15 Alpine container to docker-compose.yml - Configure persistent volume for database data - Update backend Dockerfile with OpenSSL for Prisma compatibility **Database Schema (Prisma):** - 6 tables: users, events, chat_rooms, messages, matches, ratings - Foreign key relationships and cascading deletes - Performance indexes on frequently queried columns - Unique constraints for data integrity **Prisma Setup:** - Prisma Client for database queries - Migration system with initial migration - Seed script with 4 test events and chat rooms - Database connection utility with singleton pattern **API Implementation:** - GET /api/events - List all events (with filtering and sorting) - GET /api/events/:id - Get single event with relations - Database connection test on server startup - Graceful database disconnect on shutdown **Seed Data:** - Warsaw Dance Festival 2025 - Swing Camp Barcelona 2025 - Blues Week Herräng 2025 - Krakow Swing Connection 2025 **Testing:** - Database connection verified ✅ - API endpoints returning data from PostgreSQL ✅ - Migrations applied successfully ✅ All systems operational 🚀
2025-11-12 21:56:11 +01:00
"test:watch": "jest --watch",
"prisma:generate": "prisma generate",
"prisma:migrate": "prisma migrate dev",
"prisma:seed": "node prisma/seed.js",
"prisma:studio": "prisma studio"
feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
},
feat: add JWT authentication with complete test coverage Phase 1 - Step 3: Authentication API **Backend Authentication:** - bcryptjs for password hashing (salt rounds: 10) - JWT tokens with 24h expiration - Secure password storage (never expose passwordHash) **API Endpoints:** - POST /api/auth/register - User registration - Username validation (3-50 chars, alphanumeric + underscore) - Email validation and normalization - Password validation (min 6 chars) - Duplicate email/username detection - Auto-generated avatar (ui-avatars.com) - POST /api/auth/login - User authentication - Email + password credentials - Returns JWT token + user data - Invalid credentials protection - GET /api/users/me - Get current user (protected) - Requires valid JWT token - Returns user data + stats (matches, ratings) - Token validation via middleware **Security Features:** - express-validator for input sanitization - Auth middleware for protected routes - Token verification (Bearer token) - Password never returned in responses - Proper error messages (no information leakage) **Frontend Integration:** - API service layer (frontend/src/services/api.js) - Updated AuthContext to use real API - Token storage in localStorage - Automatic token inclusion in requests - Error handling for expired/invalid tokens **Unit Tests (30 tests, 78.26% coverage):** Auth Endpoints (14 tests): - ✅ Register: success, duplicate email, duplicate username - ✅ Register validation: invalid email, short password, short username - ✅ Login: success, wrong password, non-existent user, invalid format - ✅ Protected route: valid token, no token, invalid token, malformed header Auth Utils (9 tests): - ✅ Password hashing and comparison - ✅ Different hashes for same password - ✅ JWT generation and verification - ✅ Token expiration validation - ✅ Invalid token handling All tests passing ✅ Coverage: 78.26% ✅
2025-11-12 22:16:14 +01:00
"keywords": [
"webrtc",
"p2p",
"video",
"dance",
"matchmaking"
],
feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
"author": "",
"license": "ISC",
"dependencies": {
feat: add email verification, password reset, and WSDC integration (Phase 1.5) Backend features: - AWS SES email service with HTML templates - Email verification with dual method (link + 6-digit PIN code) - Password reset workflow with secure tokens - WSDC API proxy for dancer lookup and auto-fill registration - Extended User model with verification and WSDC fields - Email verification middleware for protected routes Frontend features: - Two-step registration with WSDC ID lookup - Password strength indicator component - Email verification page with code input - Password reset flow (request + reset pages) - Verification banner for unverified users - Updated authentication context and API service Testing: - 65 unit tests with 100% coverage of new features - Tests for auth utils, email service, WSDC controller, and middleware - Integration tests for full authentication flows - Comprehensive mocking of AWS SES and external APIs Database: - Migration: add WSDC fields (firstName, lastName, wsdcId) - Migration: add email verification fields (token, code, expiry) - Migration: add password reset fields (token, expiry) Documentation: - Complete Phase 1.5 documentation - Test suite documentation and best practices - Updated session context with new features
2025-11-13 15:47:54 +01:00
"@aws-sdk/client-ses": "^3.930.0",
feat: add JWT authentication with complete test coverage Phase 1 - Step 3: Authentication API **Backend Authentication:** - bcryptjs for password hashing (salt rounds: 10) - JWT tokens with 24h expiration - Secure password storage (never expose passwordHash) **API Endpoints:** - POST /api/auth/register - User registration - Username validation (3-50 chars, alphanumeric + underscore) - Email validation and normalization - Password validation (min 6 chars) - Duplicate email/username detection - Auto-generated avatar (ui-avatars.com) - POST /api/auth/login - User authentication - Email + password credentials - Returns JWT token + user data - Invalid credentials protection - GET /api/users/me - Get current user (protected) - Requires valid JWT token - Returns user data + stats (matches, ratings) - Token validation via middleware **Security Features:** - express-validator for input sanitization - Auth middleware for protected routes - Token verification (Bearer token) - Password never returned in responses - Proper error messages (no information leakage) **Frontend Integration:** - API service layer (frontend/src/services/api.js) - Updated AuthContext to use real API - Token storage in localStorage - Automatic token inclusion in requests - Error handling for expired/invalid tokens **Unit Tests (30 tests, 78.26% coverage):** Auth Endpoints (14 tests): - ✅ Register: success, duplicate email, duplicate username - ✅ Register validation: invalid email, short password, short username - ✅ Login: success, wrong password, non-existent user, invalid format - ✅ Protected route: valid token, no token, invalid token, malformed header Auth Utils (9 tests): - ✅ Password hashing and comparison - ✅ Different hashes for same password - ✅ JWT generation and verification - ✅ Token expiration validation - ✅ Invalid token handling All tests passing ✅ Coverage: 78.26% ✅
2025-11-12 22:16:14 +01:00
"@prisma/client": "^5.8.0",
"bcryptjs": "^2.4.3",
feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
"cors": "^2.8.5",
feat: add PostgreSQL database with Prisma ORM Phase 1 - Step 2: PostgreSQL Setup **Infrastructure:** - Add PostgreSQL 15 Alpine container to docker-compose.yml - Configure persistent volume for database data - Update backend Dockerfile with OpenSSL for Prisma compatibility **Database Schema (Prisma):** - 6 tables: users, events, chat_rooms, messages, matches, ratings - Foreign key relationships and cascading deletes - Performance indexes on frequently queried columns - Unique constraints for data integrity **Prisma Setup:** - Prisma Client for database queries - Migration system with initial migration - Seed script with 4 test events and chat rooms - Database connection utility with singleton pattern **API Implementation:** - GET /api/events - List all events (with filtering and sorting) - GET /api/events/:id - Get single event with relations - Database connection test on server startup - Graceful database disconnect on shutdown **Seed Data:** - Warsaw Dance Festival 2025 - Swing Camp Barcelona 2025 - Blues Week Herräng 2025 - Krakow Swing Connection 2025 **Testing:** - Database connection verified ✅ - API endpoints returning data from PostgreSQL ✅ - Migrations applied successfully ✅ All systems operational 🚀
2025-11-12 21:56:11 +01:00
"dotenv": "^16.3.1",
feat: add JWT authentication with complete test coverage Phase 1 - Step 3: Authentication API **Backend Authentication:** - bcryptjs for password hashing (salt rounds: 10) - JWT tokens with 24h expiration - Secure password storage (never expose passwordHash) **API Endpoints:** - POST /api/auth/register - User registration - Username validation (3-50 chars, alphanumeric + underscore) - Email validation and normalization - Password validation (min 6 chars) - Duplicate email/username detection - Auto-generated avatar (ui-avatars.com) - POST /api/auth/login - User authentication - Email + password credentials - Returns JWT token + user data - Invalid credentials protection - GET /api/users/me - Get current user (protected) - Requires valid JWT token - Returns user data + stats (matches, ratings) - Token validation via middleware **Security Features:** - express-validator for input sanitization - Auth middleware for protected routes - Token verification (Bearer token) - Password never returned in responses - Proper error messages (no information leakage) **Frontend Integration:** - API service layer (frontend/src/services/api.js) - Updated AuthContext to use real API - Token storage in localStorage - Automatic token inclusion in requests - Error handling for expired/invalid tokens **Unit Tests (30 tests, 78.26% coverage):** Auth Endpoints (14 tests): - ✅ Register: success, duplicate email, duplicate username - ✅ Register validation: invalid email, short password, short username - ✅ Login: success, wrong password, non-existent user, invalid format - ✅ Protected route: valid token, no token, invalid token, malformed header Auth Utils (9 tests): - ✅ Password hashing and comparison - ✅ Different hashes for same password - ✅ JWT generation and verification - ✅ Token expiration validation - ✅ Invalid token handling All tests passing ✅ Coverage: 78.26% ✅
2025-11-12 22:16:14 +01:00
"express": "^4.18.2",
"express-validator": "^7.3.0",
feat: implement real-time chat with Socket.IO Implemented WebSocket-based real-time messaging for both event rooms and private match chats using Socket.IO with comprehensive test coverage. Backend changes: - Installed socket.io@4.8.1 for WebSocket server - Created Socket.IO server with JWT authentication middleware - Implemented event room management (join/leave/messages) - Added active users tracking with real-time updates - Implemented private match room messaging - Integrated Socket.IO with Express HTTP server - Messages are persisted to PostgreSQL via Prisma - Added 12 comprehensive unit tests (89.13% coverage) Frontend changes: - Installed socket.io-client for WebSocket connections - Created socket service layer for connection management - Updated EventChatPage with real-time messaging - Updated MatchChatPage with real-time private chat - Added connection status indicators (● Connected/Disconnected) - Disabled message input when not connected Infrastructure: - Updated nginx config to proxy WebSocket connections at /socket.io - Added Upgrade and Connection headers for WebSocket support - Set long timeouts (7d) for persistent WebSocket connections Key features: - JWT-authenticated socket connections - Room-based architecture for events and matches - Real-time message broadcasting - Active users list with automatic updates - Automatic cleanup on disconnect - Message persistence in database Test coverage: - 12 tests passing (authentication, event rooms, match rooms, disconnect, errors) - Socket.IO module: 89.13% statements, 81.81% branches, 91.66% functions - Overall coverage: 81.19% Phase 1, Step 4 completed. Ready for Phase 2 (Core Features).
2025-11-12 22:42:15 +01:00
"jsonwebtoken": "^9.0.2",
"socket.io": "^4.8.1"
feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
},
"devDependencies": {
"jest": "^29.7.0",
feat: add JWT authentication with complete test coverage Phase 1 - Step 3: Authentication API **Backend Authentication:** - bcryptjs for password hashing (salt rounds: 10) - JWT tokens with 24h expiration - Secure password storage (never expose passwordHash) **API Endpoints:** - POST /api/auth/register - User registration - Username validation (3-50 chars, alphanumeric + underscore) - Email validation and normalization - Password validation (min 6 chars) - Duplicate email/username detection - Auto-generated avatar (ui-avatars.com) - POST /api/auth/login - User authentication - Email + password credentials - Returns JWT token + user data - Invalid credentials protection - GET /api/users/me - Get current user (protected) - Requires valid JWT token - Returns user data + stats (matches, ratings) - Token validation via middleware **Security Features:** - express-validator for input sanitization - Auth middleware for protected routes - Token verification (Bearer token) - Password never returned in responses - Proper error messages (no information leakage) **Frontend Integration:** - API service layer (frontend/src/services/api.js) - Updated AuthContext to use real API - Token storage in localStorage - Automatic token inclusion in requests - Error handling for expired/invalid tokens **Unit Tests (30 tests, 78.26% coverage):** Auth Endpoints (14 tests): - ✅ Register: success, duplicate email, duplicate username - ✅ Register validation: invalid email, short password, short username - ✅ Login: success, wrong password, non-existent user, invalid format - ✅ Protected route: valid token, no token, invalid token, malformed header Auth Utils (9 tests): - ✅ Password hashing and comparison - ✅ Different hashes for same password - ✅ JWT generation and verification - ✅ Token expiration validation - ✅ Invalid token handling All tests passing ✅ Coverage: 78.26% ✅
2025-11-12 22:16:14 +01:00
"nodemon": "^3.0.2",
"prisma": "^5.8.0",
feat: implement real-time chat with Socket.IO Implemented WebSocket-based real-time messaging for both event rooms and private match chats using Socket.IO with comprehensive test coverage. Backend changes: - Installed socket.io@4.8.1 for WebSocket server - Created Socket.IO server with JWT authentication middleware - Implemented event room management (join/leave/messages) - Added active users tracking with real-time updates - Implemented private match room messaging - Integrated Socket.IO with Express HTTP server - Messages are persisted to PostgreSQL via Prisma - Added 12 comprehensive unit tests (89.13% coverage) Frontend changes: - Installed socket.io-client for WebSocket connections - Created socket service layer for connection management - Updated EventChatPage with real-time messaging - Updated MatchChatPage with real-time private chat - Added connection status indicators (● Connected/Disconnected) - Disabled message input when not connected Infrastructure: - Updated nginx config to proxy WebSocket connections at /socket.io - Added Upgrade and Connection headers for WebSocket support - Set long timeouts (7d) for persistent WebSocket connections Key features: - JWT-authenticated socket connections - Room-based architecture for events and matches - Real-time message broadcasting - Active users list with automatic updates - Automatic cleanup on disconnect - Message persistence in database Test coverage: - 12 tests passing (authentication, event rooms, match rooms, disconnect, errors) - Socket.IO module: 89.13% statements, 81.81% branches, 91.66% functions - Overall coverage: 81.19% Phase 1, Step 4 completed. Ready for Phase 2 (Core Features).
2025-11-12 22:42:15 +01:00
"socket.io-client": "^4.8.1",
feat: add JWT authentication with complete test coverage Phase 1 - Step 3: Authentication API **Backend Authentication:** - bcryptjs for password hashing (salt rounds: 10) - JWT tokens with 24h expiration - Secure password storage (never expose passwordHash) **API Endpoints:** - POST /api/auth/register - User registration - Username validation (3-50 chars, alphanumeric + underscore) - Email validation and normalization - Password validation (min 6 chars) - Duplicate email/username detection - Auto-generated avatar (ui-avatars.com) - POST /api/auth/login - User authentication - Email + password credentials - Returns JWT token + user data - Invalid credentials protection - GET /api/users/me - Get current user (protected) - Requires valid JWT token - Returns user data + stats (matches, ratings) - Token validation via middleware **Security Features:** - express-validator for input sanitization - Auth middleware for protected routes - Token verification (Bearer token) - Password never returned in responses - Proper error messages (no information leakage) **Frontend Integration:** - API service layer (frontend/src/services/api.js) - Updated AuthContext to use real API - Token storage in localStorage - Automatic token inclusion in requests - Error handling for expired/invalid tokens **Unit Tests (30 tests, 78.26% coverage):** Auth Endpoints (14 tests): - ✅ Register: success, duplicate email, duplicate username - ✅ Register validation: invalid email, short password, short username - ✅ Login: success, wrong password, non-existent user, invalid format - ✅ Protected route: valid token, no token, invalid token, malformed header Auth Utils (9 tests): - ✅ Password hashing and comparison - ✅ Different hashes for same password - ✅ JWT generation and verification - ✅ Token expiration validation - ✅ Invalid token handling All tests passing ✅ Coverage: 78.26% ✅
2025-11-12 22:16:14 +01:00
"supertest": "^6.3.3"
feat: add backend setup with Express and unit tests Backend Foundation (Phase 1 - Step 1): **Infrastructure:** - Add backend service to docker-compose.yml - Configure nginx to proxy /api/* to backend - Node.js 20 Alpine Docker container **Backend Setup:** - Express.js REST API server - CORS configuration - Request logging middleware - Error handling (404, 500) - Graceful shutdown on SIGTERM/SIGINT - Health check endpoint: GET /api/health **Testing:** - Jest + Supertest for unit tests - 7 test cases covering: - Health check endpoint - 404 error handling - CORS headers - JSON body parsing - Code coverage: 88.23% **Project Structure:** - backend/src/app.js - Express app setup - backend/src/server.js - Server entry point - backend/src/__tests__/ - Unit tests - backend/README.md - Backend documentation **Environment:** - .env.example template - Development configuration - Ready for PostgreSQL integration All tests passing ✅
2025-11-12 21:42:52 +01:00
},
"jest": {
"testEnvironment": "node",
"coveragePathIgnorePatterns": [
"/node_modules/"
],
"testMatch": [
"**/__tests__/**/*.test.js"
]
}
}
Reference in New Issue Copy Permalink